Triple
T30397875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2/3rd Machine Gun Battalion |
E773268
|
entity |
| Predicate | typeOfFireSupport |
P37559
|
FINISHED |
| Object | sustained fire |
—
|
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: sustained fire | Statement: [2/3rd Machine Gun Battalion, typeOfFireSupport, sustained fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFireSupport Context triple: [2/3rd Machine Gun Battalion, typeOfFireSupport, sustained fire]
-
A.
fireSupportType
chosen
Indicates the specific kind or category of supporting fire (such as artillery, air support, or naval gunfire) being provided in a military context.
-
B.
fireSupportRole
Indicates that one entity provides supporting fire or indirect combat assistance to another entity or operation.
-
C.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
D.
fireTowerType
Indicates the specific classification or category of a fire tower in relation to that tower.
-
E.
courseOfFireFeature
Indicates a characteristic, condition, or attribute that defines or modifies a particular course of fire in a shooting or training scenario.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: April 29, 2026, 8:03 p.m.