Triple
T3510599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Kalka River |
E74184
|
entity |
| Predicate | tacticUsedByMongols |
P1716
|
FINISHED |
| Object | feigned retreat |
—
|
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: feigned retreat | Statement: [Battle of the Kalka River, tacticUsedByMongols, feigned retreat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedByMongols Context triple: [Battle of the Kalka River, tacticUsedByMongols, feigned retreat]
-
A.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
B.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
militaryTacticsFaced
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
-
D.
hasCommonTacticOfOpponents
Indicates that two or more entities share the same tactic or strategy used by their respective opponents.
-
E.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0e1f0c8190b054d9fba16ce4b3 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.