Triple
T30455892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Cars Go |
E774859
|
entity |
| Predicate | trackNumberOnNeonBible |
P174415
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [No Cars Go, trackNumberOnNeonBible, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnNeonBible Context triple: [No Cars Go, trackNumberOnNeonBible, 9]
-
A.
trackNumberOnPhrenology
Indicates that a specific track or item is assigned a particular sequence number within the context of phrenology-related content or data.
-
B.
ringNumber
Indicates that an entity is assigned a specific ring identifier or position number within a ring-structured system or sequence.
-
C.
chronNumber
Indicates that one entity is assigned a specific chronological number or position in an ordered sequence relative to others.
-
D.
trackNumberOnMilesAhead
Indicates the specific track number assigned to the song or item titled "Miles Ahead" within a track listing or sequence.
-
E.
isTrackNumberApproximate
Indicates that the specified track number is not exact but an estimated or approximate value.
- F. None of above. chosen
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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 29, 2026, 8:09 p.m.