Triple
T9209085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myeongnyun Station |
E221064
|
entity |
| Predicate | isBelowGroundLevel |
P43725
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Myeongnyun Station, isBelowGroundLevel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBelowGroundLevel Context triple: [Myeongnyun Station, isBelowGroundLevel, yes]
-
A.
elevationBelowGround
Indicates that one entity’s elevation is located beneath the ground surface or reference ground level.
-
B.
hasUndergroundDepth
chosen
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
C.
isBelowSeaLevel
Indicates that one entity’s vertical position is lower than the standard sea level reference point.
-
D.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
E.
isElevatedOrAtGradeIn
Indicates that one entity is positioned either above ground level (elevated) or directly at ground level (at grade) within the context of another entity or environment.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b3c8c081909a688ce699928fc0 |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:26 p.m.