Triple
T38376067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Region (Vietnam) |
E893624
|
entity |
| Predicate | plannedAirport |
P194406
|
FINISHED |
| Object | Long Thanh International Airport |
—
|
NE NERFINISHED |
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: Long Thanh International Airport | Statement: [Southeast Region (Vietnam), plannedAirport, Long Thanh International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedAirport Context triple: [Southeast Region (Vietnam), plannedAirport, Long Thanh International Airport]
-
A.
parentAirport
Indicates that one airport serves as the primary or overarching facility from which another, subsidiary or associated airport is derived or managed.
-
B.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
C.
airportDesignation
Indicates that an entity is officially designated or classified as an airport.
-
D.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
-
E.
previousPrimaryAirportFor
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:31 p.m.