Triple
T5260596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ai |
E118812
|
entity |
| Predicate | tacticUsedInSecondAttack |
P1716
|
FINISHED |
| Object | ambush |
—
|
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: ambush | Statement: [Battle of Ai, tacticUsedInSecondAttack, ambush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedInSecondAttack Context triple: [Battle of Ai, tacticUsedInSecondAttack, ambush]
-
A.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
operationInSecondBattle
Indicates that an entity participated in or was involved in a military operation that took place during the second battle of a given conflict.
-
C.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
D.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
E.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcf026c8190881b6e14b962a3c9 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.