Triple
T24505326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belize–Mexico border |
E618049
|
entity |
| Predicate | adjacentToBelizeDistrict |
P68114
|
FINISHED |
| Object | Corozal District |
—
|
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: Corozal District | Statement: [Belize–Mexico border, adjacentToBelizeDistrict, Corozal District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToBelizeDistrict Context triple: [Belize–Mexico border, adjacentToBelizeDistrict, Corozal District]
-
A.
distanceFromBelizeMainland
Indicates the measured spatial distance separating a given entity from the mainland territory of Belize.
-
B.
adjacentToParaguayanDepartment
Indicates that one entity is directly next to or shares a boundary with a department located in Paraguay.
-
C.
borderTownGuatemala
Indicates that a town is located on or near the national border of Guatemala, functioning as a border town relative to that country.
-
D.
distanceFromCentralAmerica
Indicates the measured spatial distance between a given entity and the region of Central America.
-
E.
geographicallyAdjacentTo
chosen
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.