Triple
T664815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury Line |
E12836
|
entity |
| Predicate | hasRouteColor |
P9560
|
FINISHED |
| Object | yellow (on Metrolink maps) |
—
|
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: yellow (on Metrolink maps) | Statement: [Bury Line, hasRouteColor, yellow (on Metrolink maps)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteColor Context triple: [Bury Line, hasRouteColor, yellow (on Metrolink maps)]
-
A.
hasRouteColorStandard
chosen
Indicates that a route is associated with a standardized color designation used for identification or classification.
-
B.
hasCrossColor
Indicates that an entity possesses a cross-shaped marking or pattern of a specified color.
-
C.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
D.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
E.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd3d8fc8190866af5c76c08f486 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.