Triple
T27463457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité |
E693113
|
entity |
| Predicate | hasFormerRollingStock |
P29565
|
FINISHED |
| Object | MP 59 |
—
|
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 59 | Statement: [Cité, hasFormerRollingStock, MP 59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerRollingStock Context triple: [Cité, hasFormerRollingStock, MP 59]
-
A.
formerRollingStock
chosen
Indicates that an entity was previously used as rolling stock (e.g., railway vehicles) but no longer serves in that capacity.
-
B.
usesRollingStock
Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
-
C.
laterRollingStock
Indicates that one piece of rolling stock comes into use or service at a later time than another piece of rolling stock.
-
D.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
E.
previousRollingStockOrigin
Indicates that one entity is the place or source from which the immediately preceding piece of rolling stock (e.g., train car or unit) originated.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 12:51 p.m.