Triple
T24562844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miromesnil station |
E607701
|
entity |
| Predicate | hasRollingStockOnLine |
P5426
|
FINISHED |
| Object | MF 01 (Line 9) |
—
|
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: MF 01 (Line 9) | Statement: [Miromesnil station, hasRollingStockOnLine, MF 01 (Line 9)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRollingStockOnLine Context triple: [Miromesnil station, hasRollingStockOnLine, MF 01 (Line 9)]
-
A.
hasRollingStockOnDisplay
Indicates that a location or entity has railway rolling stock (such as locomotives or carriages) exhibited for public viewing.
-
B.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
C.
usesRollingStock
chosen
Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
-
D.
isBetweenStationsOnLine
Indicates that something is located or occurs between two stations along the same transit line.
-
E.
line1RollingStock
Indicates that the rolling stock (e.g., train cars or locomotives) is assigned to or operating on the first line in a multi-line rail system.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f7a244819080596718c21d0df3 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.