Triple
T2684538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallschirmjäger division |
E57451
|
entity |
| Predicate | hasTacticalMobility |
P41498
|
FINISHED |
| Object | airborne insertion |
—
|
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: airborne insertion | Statement: [Fallschirmjäger division, hasTacticalMobility, airborne insertion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTacticalMobility Context triple: [Fallschirmjäger division, hasTacticalMobility, airborne insertion]
-
A.
hasStrategicPass
Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
-
B.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
-
C.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
-
D.
hasCommonTacticOfOpponents
Indicates that two or more entities share the same tactic or strategy used by their respective opponents.
-
E.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9edba5c8190b86d6cba0f1964e2 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.