Triple
T29884219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlapanec people |
E758964
|
entity |
| Predicate | liveInRegion |
P75000
|
FINISHED |
| Object | La Montaña, Guerrero |
—
|
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: La Montaña, Guerrero | Statement: [Tlapanec people, liveInRegion, La Montaña, Guerrero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveInRegion Context triple: [Tlapanec people, liveInRegion, La Montaña, Guerrero]
-
A.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
regionOfHabitation
chosen
Indicates the geographic area or environment in which an entity typically lives or resides.
-
C.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
D.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
E.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676fc2748819094f7048111b2b407 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:59 p.m.