Triple
T20023278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IR |
E494913
|
entity |
| Predicate | usedOnRollingStockLivery |
P21786
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [IR, usedOnRollingStockLivery, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnRollingStockLivery Context triple: [IR, usedOnRollingStockLivery, yes]
-
A.
hasLivery
chosen
Indicates that one entity bears or displays the distinctive colors, markings, or branding (livery) associated with another entity.
-
B.
usesRollingStockBrand
Indicates that one entity employs or operates rolling stock manufactured under a specific brand.
-
C.
liveryFeature
Indicates a characteristic or design element that is part of a specific livery or external appearance scheme.
-
D.
rollingStockColor
Indicates the color attribute assigned to a piece of rolling stock (such as a rail vehicle) in the relationship.
-
E.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628a1ecc8190bf6ee0bedb61e0b8 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.