Triple
T12256429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Battalion, 158th Aviation Regiment |
E292113
|
entity |
| Predicate | militaryRoleCategory |
P5004
|
FINISHED |
| Object | combat support |
—
|
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: combat support | Statement: [2nd Battalion, 158th Aviation Regiment, militaryRoleCategory, combat support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRoleCategory Context triple: [2nd Battalion, 158th Aviation Regiment, militaryRoleCategory, combat support]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
C.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
D.
militaryFunction
chosen
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
E.
militaryRankScope
Indicates the hierarchical level or range of authority that a military rank applies to within an organizational or operational context.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.