Triple
T36240950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Thanh International Airport |
E891514
|
entity |
| Predicate | plannedPhases |
P40796
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Long Thanh International Airport, plannedPhases, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedPhases Context triple: [Long Thanh International Airport, plannedPhases, 3]
-
A.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
B.
redevelopmentPhasing
Indicates the planned sequence and timing in which different parts of a redevelopment project are to be carried out.
-
C.
capitalPhase
Indicates a relationship where an entity is in a particular stage or phase of capital development, investment, or funding.
-
D.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
E.
builtInPhases
chosen
Indicates that something is constructed, developed, or implemented in distinct, sequential stages or phases.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:09 p.m.