Triple
T1841699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montparnasse derailment |
E41189
|
entity |
| Predicate | distanceFallen |
P34029
|
FINISHED |
| Object | about 10–12 metres |
—
|
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: about 10–12 metres | Statement: [Montparnasse derailment, distanceFallen, about 10–12 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFallen Context triple: [Montparnasse derailment, distanceFallen, about 10–12 metres]
-
A.
fallsDownBefore
Indicates that one event or entity moves downward or collapses prior in time to another specified event or entity.
-
B.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
C.
fallsOn
Indicates that one entity descends due to gravity and comes to rest upon the surface of another entity.
-
D.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
E.
fallsIn
Indicates that one entity is located within, contained by, or geographically/administratively included inside another entity.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.