Triple
T35570854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle line Edgware Road–Gloucester Road–High Street Kensington loop |
E1027930
|
entity |
| Predicate | usesLineColour |
P183414
|
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: [Circle line Edgware Road–Gloucester Road–High Street Kensington loop, usesLineColour, yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLineColour Context triple: [Circle line Edgware Road–Gloucester Road–High Street Kensington loop, usesLineColour, yellow]
-
A.
usesTrunkLineColor
Indicates that one entity adopts or applies the trunk line color associated with another entity or system.
-
B.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
C.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
D.
servedByLineColor
Indicates that a transit service or route is operated using vehicles or infrastructure associated with a specific line color.
-
E.
isColorCodedLine
Indicates that a line is represented or distinguished using specific colors according to a coding scheme.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.