Triple
T29218498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yesstory |
E740743
|
entity |
| Predicate | notableTrackIncluded |
P143319
|
FINISHED |
| Object | Roundabout |
E202274
|
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: Roundabout | Statement: [Yesstory, notableTrackIncluded, Roundabout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTrackIncluded Context triple: [Yesstory, notableTrackIncluded, Roundabout]
-
A.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
B.
notableSongsIncluded
Indicates that certain notable or significant songs are included as part of the referenced entity (such as an album, playlist, or collection).
-
C.
notableTrackLength
Indicates that there is a track whose duration is considered significant or noteworthy in the context of the subject.
-
D.
trackIncluded
chosen
Indicates that a particular track is contained within, or forms part of, a larger collection, release, or grouping of tracks.
-
E.
notableTrackRole
Indicates that an entity has a significant or distinguished role or contribution in relation to a particular track (such as a song or recording).
- F. None of above.
Provenance (4 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a032616547c8190bc877202e43403eb |
completed | May 12, 2026, 1:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25891907f08190b492902c9931e70f |
completed | June 7, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_6a0325246abc819088e16a7fbadf40c5 |
completed | May 12, 2026, 1:03 p.m. |
Created at: April 28, 2026, 12:14 p.m.