Triple
T5174592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Junín |
E116765
|
entity |
| Predicate | typeOfCombat |
P1403
|
FINISHED |
| Object | cavalry battle |
—
|
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: cavalry battle | Statement: [Battle of Junín, typeOfCombat, cavalry battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCombat Context triple: [Battle of Junín, typeOfCombat, cavalry battle]
-
A.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
B.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
C.
introducedToCombat
Indicates that something was brought into use or implemented specifically for the purpose of addressing or mitigating a particular problem, threat, or undesirable condition.
-
D.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
E.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7971284481909e6d07b2368a4f76 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.