Triple
T35214492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolan Boogie |
E1016782
|
entity |
| Predicate | hasNotableTrackCreator |
P204307
|
FINISHED |
| Object | Marc Bolan |
E583164
|
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: Marc Bolan | Statement: [Bolan Boogie, hasNotableTrackCreator, Marc Bolan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTrackCreator Context triple: [Bolan Boogie, hasNotableTrackCreator, Marc Bolan]
-
A.
hasNotableContentCreator
Indicates that an entity is associated with a content creator who is recognized as notable or prominent.
-
B.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
C.
hasNotableAwardCreatedBy
Indicates that an award received by an entity was created or established by a specific creator or organization.
-
D.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
E.
hasBackingTrackCreator
Indicates that an entity has a creator responsible for producing its backing track.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0379a4086c8190a83df5570f737e15 |
completed | May 12, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfab878948190a511d5f0dcdf2432 |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a037049db848190a6268bf1a8a60223 |
completed | May 12, 2026, 6:24 p.m. |
| PDg | Predicate description generation | batch_6a0379a33dc48190a29f72268c8ca8a8 |
completed | May 12, 2026, 7:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.