Triple
T16971997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Curalaba |
E411707
|
entity |
| Predicate | governorOfKilledCommander |
P125443
|
FINISHED |
| Object | Governor of Chile |
—
|
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: Governor of Chile | Statement: [Battle of Curalaba, governorOfKilledCommander, Governor of Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorOfKilledCommander Context triple: [Battle of Curalaba, governorOfKilledCommander, Governor of Chile]
-
A.
alliedCommanderKilled
Indicates that a commander belonging to an allied force has been killed.
-
B.
commanderOfDefeatedSide
Indicates that the subject is the military or strategic leader of the side that lost in a particular conflict or battle.
-
C.
commanderDeath
Indicates that an entity dies while serving in the role of a commander or as the leader in a command position.
-
D.
capturedCommander
Indicates that one party has taken a military commander from another party into custody or control.
-
E.
notableCommanderKilledInAction
Indicates that a notable military commander associated with an entity was killed in action.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ad04ac81909a11b45be567613a |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:31 a.m.