Triple
T17555009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlaltizapán de Zapata Municipality |
E427567
|
entity |
| Predicate | hasRevolutionaryHistory |
P107990
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tlaltizapán de Zapata Municipality, hasRevolutionaryHistory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevolutionaryHistory Context triple: [Tlaltizapán de Zapata Municipality, hasRevolutionaryHistory, true]
-
A.
hasRevolutionaryHeritage
chosen
Indicates that an entity possesses a background, lineage, or history closely connected to revolutionary movements, activities, or figures.
-
B.
revolutionaryName
Indicates that the specified name is the one by which a revolutionary individual is known or identified.
-
C.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
D.
chronologyWithinRevolution
Indicates that one event or time period occurs within the temporal span of a specified revolution.
-
E.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562205c08190a7580a762d61b1e3 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.