Triple
T27238123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MZBZ |
E687121
|
entity |
| Predicate | servesAsPrimaryEntryPointByAirTo |
P189420
|
FINISHED |
| Object | Belize |
—
|
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: Belize | Statement: [MZBZ, servesAsPrimaryEntryPointByAirTo, Belize]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsPrimaryEntryPointByAirTo Context triple: [MZBZ, servesAsPrimaryEntryPointByAirTo, Belize]
-
A.
hasPrimaryAirportRole
Indicates that an entity holds the main or principal functional role associated with an airport.
-
B.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
C.
isMainAirportStopFor
Indicates that a given airport serves as the primary or principal stop for a specified route, service, or transportation connection.
-
D.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
-
E.
previousPrimaryAirportFor
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
- F. None of above. chosen
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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 27, 2026, 10:35 a.m.