Triple
T21641624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gizo |
E534100
|
entity |
| Predicate | hasAirport |
P105
|
FINISHED |
| Object | Gizo 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: Gizo Airport | Statement: [Gizo, hasAirport, Gizo Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gizo Airport Context triple: [Gizo, hasAirport, Gizo Airport]
-
A.
Gizo Airport
chosen
Gizo Airport is a small regional airfield serving the town of Gizo and surrounding areas in the Western Province of the Solomon Islands.
-
B.
Amausi Airport
Amausi Airport is the former name of Chaudhary Charan Singh International Airport, the main airport serving Lucknow in the Indian state of Uttar Pradesh.
-
C.
Gillam Airport
Gillam Airport is a small regional airport in Gillam, Manitoba, Canada, providing air transport services to the remote northern community and surrounding areas.
-
D.
Kasiguncu Airport
Kasiguncu Airport is a regional airport serving the town of Poso in Central Sulawesi, Indonesia.
-
E.
Totegegie Airport
Totegegie Airport is the main air gateway serving the remote Gambier Islands in French Polynesia, providing vital connections to other parts of the territory.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef53917f3c81909e7f4074beecefd3 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 16, 2026, 6:35 p.m.