Triple
T25026712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiamen Airlines |
E626728
|
entity |
| Predicate | longHaulDestinationsRegion |
P6093
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [Xiamen Airlines, longHaulDestinationsRegion, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longHaulDestinationsRegion Context triple: [Xiamen Airlines, longHaulDestinationsRegion, North America]
-
A.
primaryLongHaulRegion
Indicates the main long-distance geographic region in which an entity primarily operates or is associated for long-haul activities.
-
B.
typicalDestinationsRegion
chosen
Indicates that a region is a common or characteristic destination area associated with something (such as travelers, routes, or activities).
-
C.
transcontinentalRegion
Indicates a region that spans or extends across more than one continent.
-
D.
longitudeRegion
Indicates that an entity is located within or associated with a specific longitudinal region on the Earth’s surface.
-
E.
overseasRegionOf
Indicates that one region is an overseas territory or administrative division belonging to another country or primary region.
- F. None of above.
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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10cbc2a74481909c1e1a51e33ba3b0 |
completed | May 22, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:07 a.m.