Triple
T36827013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perote |
E910036
|
entity |
| Predicate | isLocatedInHighlandRegion |
P165213
|
FINISHED |
| Object | Trans-Mexican Volcanic Belt |
—
|
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: Trans-Mexican Volcanic Belt | Statement: [Perote, isLocatedInHighlandRegion, Trans-Mexican Volcanic Belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInHighlandRegion Context triple: [Perote, isLocatedInHighlandRegion, Trans-Mexican Volcanic Belt]
-
A.
isInHighlandRegion
chosen
Indicates that an entity is located within a highland or elevated geographic region.
-
B.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
-
C.
isHighlandConstituency
Indicates that a given constituency is located within or classified as part of the Highland region.
-
D.
isInValleyOrMountainRegion
Indicates that an entity is located within either a valley area or a mountainous region.
-
E.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:13 p.m.