Triple
T37805604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loader Bot |
E942490
|
entity |
| Predicate | combatCapabilities |
P56184
|
FINISHED |
| Object | heavy weapons |
—
|
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: heavy weapons | Statement: [Loader Bot, combatCapabilities, heavy weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatCapabilities Context triple: [Loader Bot, combatCapabilities, heavy weapons]
-
A.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
B.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
C.
militaryCapabilityInvolved
Indicates that a military capability (such as forces, equipment, or operational assets) participates in or is implicated in a specific event, activity, or situation.
-
D.
operationalCapability
chosen
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
-
E.
defensiveCapability
Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:19 p.m.