Triple
T5351485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Byrds |
E102587
|
entity |
| Predicate | pioneeredStyle |
P1851
|
FINISHED |
| Object | folk rock |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: folk rock | Statement: [The Byrds, pioneeredStyle, folk rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pioneeredStyle Context triple: [The Byrds, pioneeredStyle, folk rock]
-
A.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
B.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
C.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
D.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
E.
artisticStyle
chosen
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd861188ac81908ef2b1f25cc6c864 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.