Triple
T25430864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FUN |
E637248
|
entity |
| Predicate | airportServesPopulationCenter |
P75084
|
FINISHED |
| Object | Funafuti atoll |
E1507216
|
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: Funafuti atoll | Statement: [FUN, airportServesPopulationCenter, Funafuti atoll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportServesPopulationCenter Context triple: [FUN, airportServesPopulationCenter, Funafuti atoll]
-
A.
majorPopulationCenter
Indicates that a location functions as a primary hub of population concentration and activity within a region.
-
B.
isMajorRegionalAirportFor
chosen
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
C.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
D.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
E.
hasAirportCenter
Indicates that an airport is centrally located within, or serves as the main air transport hub for, a specified area or 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a278913a82c8190aee83a61e55212ff |
completed | June 9, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:58 p.m.