Triple
T18863593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Kiribati |
E461374
|
entity |
| Predicate | internationalServiceArea |
P66819
|
FINISHED |
| Object | regional Pacific routes |
—
|
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: regional Pacific routes | Statement: [Air Kiribati, internationalServiceArea, regional Pacific routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalServiceArea Context triple: [Air Kiribati, internationalServiceArea, regional Pacific routes]
-
A.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
B.
hasInternationalDistrict
Indicates that an entity possesses, contains, or is associated with a designated international district within its boundaries or scope.
-
C.
servesCrossBorderArea
chosen
Indicates that a service, activity, or function extends beyond a single jurisdiction and operates across national or regional borders.
-
D.
hasInternationalService
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
-
E.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a304d4819092f14b7932d01afe |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.