Triple
T9050340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tân Sơn Nhất area |
E216865
|
entity |
| Predicate | airportTypePresent |
P86085
|
FINISHED |
| Object | civilian airport |
—
|
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: civilian airport | Statement: [Tân Sơn Nhất area, airportTypePresent, civilian airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportTypePresent Context triple: [Tân Sơn Nhất area, airportTypePresent, civilian airport]
-
A.
isLocatedAtAirportType
Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
-
B.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
C.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
-
D.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
-
E.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b52cc1881909fb011d9a8af2e18 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.