Triple
T28336018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko Lanta Yai |
E717671
|
entity |
| Predicate | alternativeAirport |
P40597
|
FINISHED |
| Object | Trang 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: Trang Airport | Statement: [Ko Lanta Yai, alternativeAirport, Trang Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeAirport Context triple: [Ko Lanta Yai, alternativeAirport, Trang Airport]
-
A.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
B.
otherMainAirportInCountry
Indicates that one airport is another primary airport located within the same country as the first.
-
C.
otherAirportOfCity
Indicates that the subject airport is another airport serving the same city as the object airport.
-
D.
associatedAirportReplaced
Indicates that one airport in an association has been superseded or replaced by another airport.
-
E.
hasSecondaryAirport
chosen
Indicates that an entity is associated with an additional, typically smaller or alternative, airport beyond its primary one.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:36 a.m.