Triple
T17616858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruoholahti station |
E429105
|
entity |
| Predicate | hasDepthBelowGround |
P87151
|
FINISHED |
| Object | approximately 20 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: approximately 20 metres | Statement: [Ruoholahti station, hasDepthBelowGround, approximately 20 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepthBelowGround Context triple: [Ruoholahti station, hasDepthBelowGround, approximately 20 metres]
-
A.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
B.
elevationBelowGround
Indicates that one entity’s elevation is located beneath the ground surface or reference ground level.
-
C.
buriedDepth
Indicates the depth at which one entity is buried beneath a reference surface or another entity.
-
D.
hasRegolithDepth
Indicates the depth or thickness of a layer of regolith present on a surface or object.
-
E.
depthBelowSurfaceInMeters
chosen
Indicates the vertical distance, measured in meters, that something is located below a reference surface level.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d32991c81909801161b0a416c94 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.