Triple
T35411882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMD-2 |
E1023533
|
entity |
| Predicate | antiTankMissileCompatibleWith |
P116373
|
FINISHED |
| Object | 9M113 Konkurs |
—
|
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: 9M113 Konkurs | Statement: [BMD-2, antiTankMissileCompatibleWith, 9M113 Konkurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiTankMissileCompatibleWith Context triple: [BMD-2, antiTankMissileCompatibleWith, 9M113 Konkurs]
-
A.
compatibleMissile
chosen
Indicates that a missile can be correctly used with, mounted on, or launched by a given platform or launcher system.
-
B.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
C.
usesMainBattleTank
Indicates that an entity employs or operates a main battle tank as part of its activities or capabilities.
-
D.
associatedWithMissile
Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
-
E.
hasTurrets
Indicates that an entity is equipped with or possesses one or more turrets.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79568d298819096853fa97b179305 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.