Triple
T22721479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q Line |
E561872
|
entity |
| Predicate | usesTrunkLineColor |
P149452
|
FINISHED |
| Object | Broadway Line color (yellow) |
—
|
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: Broadway Line color (yellow) | Statement: [Q Line, usesTrunkLineColor, Broadway Line color (yellow)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTrunkLineColor Context triple: [Q Line, usesTrunkLineColor, Broadway Line color (yellow)]
-
A.
trunkLineColorRepresents
Indicates that the color of a trunk line is used to signify or encode a particular meaning, status, or category associated with that line.
-
B.
trackColor
Indicates the color associated with a given track in a context such as audio, video, or data sequencing.
-
C.
hasTrimLineColor
Indicates that an entity has a specific color applied to the trim or outline portion of its visual representation.
-
D.
colorOfTrailMarkings
Indicates the relationship specifying what color the trail’s markings are.
-
E.
servedByLineColor
Indicates that a transit service or route is operated using vehicles or infrastructure associated with a specific line color.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17911a4fc81908a125209aea77e22 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:19 p.m.