Triple
T25430875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FUN |
E637248
|
entity |
| Predicate | airportServesGovernment |
P38514
|
FINISHED |
| Object | Government of Tuvalu |
—
|
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: Government of Tuvalu | Statement: [FUN, airportServesGovernment, Government of Tuvalu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportServesGovernment Context triple: [FUN, airportServesGovernment, Government of Tuvalu]
-
A.
airportServesMilitaryTraffic
Indicates that the airport accommodates or handles military air traffic in addition to any other types of traffic.
-
B.
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.
-
C.
airportServed
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
-
D.
isStateCapitalAirport
Indicates that an airport serves as the primary airport for a city that is the capital of a state.
-
E.
airportUse
chosen
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 1:58 p.m.