Triple
T27463458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité |
E693113
|
entity |
| Predicate | hasCurrentRollingStock |
P5426
|
FINISHED |
| Object | MP 89 |
—
|
NE NERFINISHED |
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: MP 89 | Statement: [Cité, hasCurrentRollingStock, MP 89]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentRollingStock Context triple: [Cité, hasCurrentRollingStock, MP 89]
-
A.
usesRollingStock
chosen
Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
-
B.
hasRollingStockOnDisplay
Indicates that a location or entity has railway rolling stock (such as locomotives or carriages) exhibited for public viewing.
-
C.
hasRollingStockFeature
Indicates that a piece of rolling stock possesses a specific feature, characteristic, or equipment.
-
D.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
E.
usesRollingStockCompatibleWith
Indicates that one entity operates using rolling stock that is technically and operationally compatible with the rolling stock standards or systems associated with another entity.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 12:51 p.m.