Triple
T25907418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eloxochitlán |
E652789
|
entity |
| Predicate | geoparkStatus |
P74959
|
FINISHED |
| Object | within UNESCO Global Geopark |
—
|
LITERAL 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: within UNESCO Global Geopark | Statement: [Eloxochitlán, geoparkStatus, within UNESCO Global Geopark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geoparkStatus Context triple: [Eloxochitlán, geoparkStatus, within UNESCO Global Geopark]
-
A.
geoparkNetwork
chosen
Indicates that a location or area is part of, associated with, or recognized within a designated geopark network.
-
B.
unescoGlobalGeoparkDesignationYear
Indicates the year in which a site received its official designation as a UNESCO Global Geopark.
-
C.
hasArchaeologicalParkStatus
Indicates that an entity has been officially designated and recognized as an archaeological park.
-
D.
countryProtectedAreaStatus
Indicates the legal or administrative protection status that a country assigns to a specific area or region.
-
E.
geologicalStatus
Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c15b348190a7f00745b6475b28 |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:27 a.m.