Triple
T6926808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury Metrolink line |
E160330
|
entity |
| Predicate | hasColourOnSystemMap |
P69958
|
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: [Bury Metrolink line, hasColourOnSystemMap, yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColourOnSystemMap Context triple: [Bury Metrolink line, hasColourOnSystemMap, yellow]
-
A.
hasColorOnRouteMap
chosen
Indicates that a specific color is used to represent an entity (such as a route or line) on a route map.
-
B.
isOnSystemMap
Indicates that an entity is currently displayed or represented on a particular system map.
-
C.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
D.
hasPylonColor
Indicates that an entity (such as a pylon or structure) possesses a specific color as one of its attributes.
-
E.
hasColourScheme
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1aa9c48190b63a04be2ed9e266 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.