Triple
T33683784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIM-162 ESSM |
E862972
|
entity |
| Predicate | compatibleWithCombatSystem |
P192587
|
FINISHED |
| Object | AEGIS Combat System |
—
|
NE NERFINISHED |
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: AEGIS Combat System | Statement: [RIM-162 ESSM, compatibleWithCombatSystem, AEGIS Combat System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleWithCombatSystem Context triple: [RIM-162 ESSM, compatibleWithCombatSystem, AEGIS Combat System]
-
A.
usesCombatSystem
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
B.
combatSystemFeature
Indicates that one entity is a feature, mechanic, or component belonging to or used within another entity’s combat system.
-
C.
hasCombatType
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
-
D.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: May 1, 2026, 1:43 a.m.