Triple
T24798740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altamirano, Chiapas |
E620460
|
entity |
| Predicate | hasHistoricalEventAssociation |
P2107
|
FINISHED |
| Object | Zapatista movement in Chiapas |
—
|
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: Zapatista movement in Chiapas | Statement: [Altamirano, Chiapas, hasHistoricalEventAssociation, Zapatista movement in Chiapas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalEventAssociation Context triple: [Altamirano, Chiapas, hasHistoricalEventAssociation, Zapatista movement in Chiapas]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
C.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
D.
historicalEntityAssociated
Indicates that one entity has a documented historical connection, relevance, or involvement with another entity.
-
E.
dateOfHistoricalAssociation
Indicates the specific date or time period during which a notable historical association, connection, or event between entities took place.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4:49 a.m.