Triple
T32690610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Advanced Surface to Air Missile System |
E835845
|
entity |
| Predicate | firstDeployment |
P3273
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Norwegian Advanced Surface to Air Missile System, firstDeployment, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDeployment Context triple: [Norwegian Advanced Surface to Air Missile System, firstDeployment, 1990s]
-
A.
firstDeploymentContext
Indicates the context, environment, or situation in which something (typically a system, product, or capability) is initially deployed or put into operational use.
-
B.
primaryDeployment
Indicates that one deployment is designated as the main or most important deployment among multiple possible deployments for an entity.
-
C.
firstDeploymentPlatform
Indicates the platform on which something (such as a product, service, or software) was initially deployed or launched.
-
D.
firstLargeDeployment
Indicates that this is the initial instance in which something is deployed at a large or significant scale.
-
E.
firstDeployed
chosen
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:09 a.m.