Triple
T25613877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tpp (Pisaflores Tepehua) |
E642107
|
entity |
| Predicate | hasVarietyRelation |
P45557
|
FINISHED |
| Object | Huehuetla Tepehua |
—
|
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: Huehuetla Tepehua | Statement: [tpp (Pisaflores Tepehua), hasVarietyRelation, Huehuetla Tepehua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVarietyRelation Context triple: [tpp (Pisaflores Tepehua), hasVarietyRelation, Huehuetla Tepehua]
-
A.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
B.
hasVarietyWithinGroup
Indicates that one group or category contains multiple distinct types, forms, or variations within it.
-
C.
hasVarietyOf
Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
-
D.
hasNeighboringVariety
chosen
Indicates that one variety is geographically or spatially adjacent to another variety.
-
E.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9e57720819080092db441fd60ef |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:43 p.m.