Triple
T8241602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall Station (Busan Metro) |
E192547
|
entity |
| Predicate | isLocatedUnderground |
P42731
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [City Hall Station (Busan Metro), isLocatedUnderground, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedUnderground Context triple: [City Hall Station (Busan Metro), isLocatedUnderground, true]
-
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.
isUndergroundOnly
Indicates that something exists, operates, or is accessible exclusively below ground level and not above ground.
-
C.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
D.
subterranean
chosen
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
E.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783f67708190a4e1c4078c3a6fb0 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.