Triple
T34669741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Thanh International Airport |
E890344
|
entity |
| Predicate | designCapacityPhase1 |
P198610
|
FINISHED |
| Object | 25 million passengers per year |
—
|
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: 25 million passengers per year | Statement: [Long Thanh International Airport, designCapacityPhase1, 25 million passengers per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCapacityPhase1 Context triple: [Long Thanh International Airport, designCapacityPhase1, 25 million passengers per year]
-
A.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
B.
stageCapacity
Indicates the maximum number of people or amount of occupancy that a particular stage can accommodate.
-
C.
productionCapacity
Indicates the maximum amount of output an entity can produce within a given time or resource constraint.
-
D.
dailyCapacity
Indicates the maximum amount of something that can be produced, processed, or handled within a single day.
-
E.
capacityPerSide
Indicates the maximum quantity or volume that each individual side or unit in a pair can hold or accommodate.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
| PDg | Predicate description generation | batch_69fef5cec8208190b85665ab6a511a08 |
completed | May 9, 2026, 8:52 a.m. |
Created at: May 1, 2026, 2:05 a.m.