Triple
T20297039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiesel 2 Ozelot |
E505376
|
entity |
| Predicate | typeOfMissile |
P75754
|
FINISHED |
| Object | infrared-guided surface-to-air missile |
—
|
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: infrared-guided surface-to-air missile | Statement: [Wiesel 2 Ozelot, typeOfMissile, infrared-guided surface-to-air missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMissile Context triple: [Wiesel 2 Ozelot, typeOfMissile, infrared-guided surface-to-air missile]
-
A.
missileClass
Indicates the classification or type category assigned to a missile within a defined system or taxonomy.
-
B.
missileTypeCarried
chosen
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
C.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
-
D.
missileWeight
Indicates the weight or mass associated with a missile in the relationship.
-
E.
numberOfMissilesPerLauncher
Indicates the quantity of missiles assigned to or carried by each individual launcher.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677095fb481909806214da4002b59 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:16 a.m.