Triple
T32312913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Osan |
E825548
|
entity |
| Predicate | USAntiTankWeapons |
P110549
|
FINISHED |
| Object | 2.36-inch bazookas |
—
|
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: 2.36-inch bazookas | Statement: [Battle of Osan, USAntiTankWeapons, 2.36-inch bazookas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USAntiTankWeapons Context triple: [Battle of Osan, USAntiTankWeapons, 2.36-inch bazookas]
-
A.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
B.
isMilitaryAssetOf
chosen
Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
-
C.
enemyMilitaryAsset
Indicates that one entity is a military asset belonging to or controlled by an enemy force relative to the other entity.
-
D.
tankClass
Indicates that an entity belongs to, or is categorized under, a particular class or type of tank.
-
E.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb8755481908645da7ceef44e17 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.