Triple
T8386159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huns |
E197823
|
entity |
| Predicate | warfareTactics |
P30685
|
FINISHED |
| Object | hit-and-run tactics |
—
|
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: hit-and-run tactics | Statement: [Huns, warfareTactics, hit-and-run tactics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warfareTactics Context triple: [Huns, warfareTactics, hit-and-run tactics]
-
A.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
B.
militaryStrategy
Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
-
C.
militaryTacticsFaced
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
-
D.
militaryDoctrine
Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by another entity.
-
E.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e1bcdc81909111aa33ee996e0a |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.