Triple
T36085434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunnel Vision |
E1043760
|
entity |
| Predicate | hasBillboardPeakPosition |
P30368
|
FINISHED |
| Object | 6 on Billboard Hot 100 |
—
|
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: 6 on Billboard Hot 100 | Statement: [Tunnel Vision, hasBillboardPeakPosition, 6 on Billboard Hot 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBillboardPeakPosition Context triple: [Tunnel Vision, hasBillboardPeakPosition, 6 on Billboard Hot 100]
-
A.
hasBillboardCountrySingles
Indicates that an entity has released one or more singles that have appeared on the Billboard country music charts.
-
B.
hasHitOnBillboardHot100
Indicates that an entity (typically a song or artist) has appeared as a ranked entry on the Billboard Hot 100 music chart.
-
C.
chartPositionUSBillboardHot100Peak
chosen
Indicates the highest ranking an item has ever reached on the US Billboard Hot 100 chart.
-
D.
hasBillboardStar
Indicates that an entity has been awarded or features a star on a billboard, signifying recognition or promotion.
-
E.
hasBillboard200NumberOne
Indicates that an entity (typically an album or song) has reached the number one position on the Billboard 200 chart.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:08 p.m.