Triple
T36503862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Burnette |
E899407
|
entity |
| Predicate | hasRelativeInMusic |
P204903
|
FINISHED |
| Object | Dorsey Burnette |
E1791902
|
NE 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: Dorsey Burnette | Statement: [Johnny Burnette, hasRelativeInMusic, Dorsey Burnette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeInMusic Context triple: [Johnny Burnette, hasRelativeInMusic, Dorsey Burnette]
-
A.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
relatesToInstrument
Indicates a relationship where one entity is associated with, involves, or makes use of a particular instrument or tool.
-
C.
hasMusicalDirection
Indicates that one entity is responsible for guiding, supervising, or determining the musical interpretation and performance of another entity.
-
D.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
E.
usesMusicalElement
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
- F. None of above. chosen
Provenance (5 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f900b49c8190bfa9cfe94595216f |
completed | June 23, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.