Triple
T3375718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Line 1 (Millennium Underground) |
E71061
|
entity |
| Predicate | colorOnSystemMaps |
P34403
|
FINISHED |
| Object | 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: yellow | Statement: [Metro Line 1 (Millennium Underground), colorOnSystemMaps, yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorOnSystemMaps Context triple: [Metro Line 1 (Millennium Underground), colorOnSystemMaps, yellow]
-
A.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
B.
circuitColorOnMaps
Indicates that a circuit is represented with a specific color on one or more maps.
-
C.
isOnSystemMap
Indicates that an entity is currently displayed or represented on a particular system map.
-
D.
mapColorBlueLine
Indicates that a map is rendered or highlighted using a blue-colored line to represent a particular feature or path.
-
E.
mapColorLine
chosen
Indicates a relationship where a specific color is assigned to or associated with a particular line (such as a route, path, or boundary) on a map.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e5fc6c81909ff582611751096d |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.