Triple
T12645126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Battle of the Matanikau |
E302001
|
entity |
| Predicate | primaryAxisOfCombat |
P106165
|
FINISHED |
| Object | west of Lunga perimeter |
—
|
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: west of Lunga perimeter | Statement: [Third Battle of the Matanikau, primaryAxisOfCombat, west of Lunga perimeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAxisOfCombat Context triple: [Third Battle of the Matanikau, primaryAxisOfCombat, west of Lunga perimeter]
-
A.
primaryCombat
Indicates that one entity is the main or principal opponent that another entity engages with in combat.
-
B.
primaryArms
Indicates that the subject possesses or uses the specified arms or weapons as its main or most important set.
-
C.
mainCombatant
Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
-
D.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
-
E.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:17 p.m.