Triple
T18239122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peacekeeper ICBM |
E436759
|
entity |
| Predicate | peakDeployedQuantity |
P92496
|
FINISHED |
| Object | 50 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: 50 missiles | Statement: [Peacekeeper ICBM, peakDeployedQuantity, 50 missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDeployedQuantity Context triple: [Peacekeeper ICBM, peakDeployedQuantity, 50 missiles]
-
A.
deploymentPeakNumber
chosen
Indicates the maximum number of deployments (or deployment instances) reached during a specified period or under given conditions.
-
B.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
C.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
D.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
E.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e19d9881908d6a227528241e4a |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.