Triple
T24562828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miromesnil station |
E607701
|
entity |
| Predicate | platformDepth |
P156339
|
FINISHED |
| Object | underground |
—
|
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: underground | Statement: [Miromesnil station, platformDepth, underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformDepth Context triple: [Miromesnil station, platformDepth, underground]
-
A.
platformHeight
Indicates the vertical distance or elevation of a platform relative to a defined reference level.
-
B.
plateInterfaceDepthRange
Indicates the range of depths over which two tectonic plates are in contact or interacting at their interface.
-
C.
platformLength
Indicates that one entity specifies the physical length or extent of a platform associated with another entity.
-
D.
platformSize
Indicates the relative or absolute size or dimensions of a platform in relation to something else.
-
E.
depthMetresApprox
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
- 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_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. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.