Triple
T29118188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1857 of Mexico |
E737103
|
entity |
| Predicate | conflictStartRelated |
P170415
|
FINISHED |
| Object | Reform War (1857–1861) |
—
|
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: Reform War (1857–1861) | Statement: [Constitution of 1857 of Mexico, conflictStartRelated, Reform War (1857–1861)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictStartRelated Context triple: [Constitution of 1857 of Mexico, conflictStartRelated, Reform War (1857–1861)]
-
A.
conflictBeginsFor
Indicates the point in time or event at which a conflict starts for a particular party or set of parties.
-
B.
conflictBeganOver
Indicates that a conflict was initiated due to or in response to a particular cause, issue, or trigger.
-
C.
warStartRelatedConflict
Indicates that the start of a war is causally or contextually connected to another conflict or set of conflicts.
-
D.
conflictRelation
Indicates a relationship in which two or more entities are in opposition, disagreement, or incompatibility, often involving competing goals, interests, or actions.
-
E.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
- F. None of above. chosen
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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 28, 2026, 11:23 a.m.