Triple
T8849920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenger air defense system |
E210611
|
entity |
| Predicate | totalReadyToFireMissiles |
P84980
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Avenger air defense system, totalReadyToFireMissiles, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalReadyToFireMissiles Context triple: [Avenger air defense system, totalReadyToFireMissiles, 8]
-
A.
numberOfDeployedMissilesPeak
Indicates the maximum number of missiles that were deployed at any point in time.
-
B.
maximumWarheadsPerMissile
Indicates the greatest number of warheads that a single missile is allowed or able to carry.
-
C.
nuclearArsenalStatus
Indicates the condition or level of development, deployment, or readiness of an entity’s nuclear weapons capability.
-
D.
hasFireMissionCapability
Indicates that an entity possesses the ability to plan, coordinate, or execute fire missions (such as artillery or indirect fire support) as part of combat operations.
-
E.
militaryBranchPreparedFor
Indicates that a specific military branch is organized, equipped, and trained to respond to or engage in a particular mission, operation, or type of conflict.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60abb0748190af41d4e1f419e39c |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:49 p.m.