Triple
T32276466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cerro Corá |
E824559
|
entity |
| Predicate | finalEngagementOf |
P21957
|
FINISHED |
| Object | War of the Triple Alliance |
—
|
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: War of the Triple Alliance | Statement: [Battle of Cerro Corá, finalEngagementOf, War of the Triple Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalEngagementOf Context triple: [Battle of Cerro Corá, finalEngagementOf, War of the Triple Alliance]
-
A.
isFinalEngagementOf
chosen
Indicates that a given engagement is the last or concluding engagement in a sequence or series of engagements involving the same entities.
-
B.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
C.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
D.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
E.
finalService
Indicates that a service represents the last or concluding service in a sequence, process, or lifecycle.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 1, 2026, 12:43 a.m.