Triple
T25748053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incheon Airport Maglev |
E648394
|
entity |
| Predicate | plannedExtensions |
P54844
|
FINISHED |
| Object | Phase 2 to Terminal 2 |
—
|
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: Phase 2 to Terminal 2 | Statement: [Incheon Airport Maglev, plannedExtensions, Phase 2 to Terminal 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedExtensions Context triple: [Incheon Airport Maglev, plannedExtensions, Phase 2 to Terminal 2]
-
A.
plannedExtensionTo
chosen
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
B.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
C.
plannedExtensionLength
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
D.
plannedExtensionProvince
Indicates that a planned extension or expansion is intended to occur within the specified province.
-
E.
plannedExpansion
Indicates that an entity has a scheduled or intended increase in size, capacity, scope, or presence in the future.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 3:54 a.m.