Triple
T36052268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Marcos Tlacoyalco Popoloca |
E1042841
|
entity |
| Predicate | primaryLocationMunicipality |
P136244
|
FINISHED |
| Object | San Marcos Tlacoyalco locality |
E1042841
|
NE 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: San Marcos Tlacoyalco locality | Statement: [San Marcos Tlacoyalco Popoloca, primaryLocationMunicipality, San Marcos Tlacoyalco locality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationMunicipality Context triple: [San Marcos Tlacoyalco Popoloca, primaryLocationMunicipality, San Marcos Tlacoyalco locality]
-
A.
mainMunicipality
Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
-
B.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
C.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
-
D.
municipalityName
Indicates the official name assigned to a municipality.
-
E.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
- F. None of above.
Provenance (4 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cba0efc88190bc9ca100bffd95bd |
completed | June 22, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.