Triple
T9050255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SGN |
E216863
|
entity |
| Predicate | alternativeNameContext |
P78012
|
FINISHED |
| Object | Ho Chi Minh City Airport code |
—
|
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: Ho Chi Minh City Airport code | Statement: [SGN, alternativeNameContext, Ho Chi Minh City Airport code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeNameContext Context triple: [SGN, alternativeNameContext, Ho Chi Minh City Airport code]
-
A.
alternativeNameMeaning
Indicates that one entity expresses the meaning or interpretation of an alternative name used for another entity.
-
B.
hasAlternativeNameForSameCity
Indicates that one city name is an alternative or variant name referring to the same city as another name.
-
C.
namedInContextOf
Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
-
D.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
E.
alsoKnownThrough
chosen
Indicates that an entity is recognized or identified by means of another entity, such as a source, context, or intermediary, through which its alternative name or identity is known.
- 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_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. |
Created at: March 30, 2026, 7:10 p.m.