Triple
T3747402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Korea Air Force |
E81240
|
entity |
| Predicate | operatesMissileType |
P20224
|
FINISHED |
| Object | surface-to-air missiles |
—
|
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: surface-to-air missiles | Statement: [Republic of Korea Air Force, operatesMissileType, surface-to-air missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesMissileType Context triple: [Republic of Korea Air Force, operatesMissileType, surface-to-air missiles]
-
A.
usesMissileSystem
chosen
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
B.
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.
-
C.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
D.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
E.
approximateNumberOfMissilesEliminated
Indicates the estimated quantity of missiles that have been neutralized or removed.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.