Triple
T14739792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Karnal (1739) |
E346313
|
entity |
| Predicate | tacticsUsedByMughals |
P115577
|
FINISHED |
| Object | heavy cavalry charges |
—
|
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: heavy cavalry charges | Statement: [Battle of Karnal (1739), tacticsUsedByMughals, heavy cavalry charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsUsedByMughals Context triple: [Battle of Karnal (1739), tacticsUsedByMughals, heavy cavalry charges]
-
A.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
B.
tacticsUsedBySpanish
Indicates that certain tactics or strategies are employed or carried out by Spanish forces, groups, or individuals.
-
C.
primaryTacticOttomans
Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
-
D.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
E.
militaryTacticsFaced
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7345680819093e901233a064e48 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:29 a.m.