Triple
T36246579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenejapa |
E891677
|
entity |
| Predicate | isHighlandMunicipality |
P78502
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tenejapa, isHighlandMunicipality, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighlandMunicipality Context triple: [Tenejapa, isHighlandMunicipality, yes]
-
A.
isMountainMunicipality
chosen
Indicates that a municipality is classified as being located in a mountainous area or characterized by predominantly mountainous terrain.
-
B.
isInHighlandRegion
Indicates that an entity is located within a highland or elevated geographic region.
-
C.
isHighlandConstituency
Indicates that a given constituency is located within or classified as part of the Highland region.
-
D.
isUplandMunicipalityOf
Indicates that a municipality is located in an upland (higher elevation) area relative to a specified region or reference point.
-
E.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5d39b948190a847f58b49a846e2 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.