Triple
T3375730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Line 1 (Millennium Underground) |
E71061
|
entity |
| Predicate | rollingStockColor |
P48066
|
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), rollingStockColor, yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollingStockColor Context triple: [Metro Line 1 (Millennium Underground), rollingStockColor, yellow]
-
A.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
B.
rollingStockFamily
Indicates a relationship where a piece of rolling stock belongs to, or is classified under, a particular family or series of related rolling stock designs.
-
C.
rollingStockLength
Indicates the length measurement of a piece of rolling stock in a rail or transit system.
-
D.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
E.
rollingStockOperator
Indicates that an entity operates or manages rolling stock, such as trains or rail vehicles, in a railway system.
- 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_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. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:13 p.m.