Triple
T12753590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegis Ballistic Missile Defense |
E304797
|
entity |
| Predicate | initialDeployment |
P55166
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Aegis Ballistic Missile Defense, initialDeployment, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialDeployment Context triple: [Aegis Ballistic Missile Defense, initialDeployment, early 2000s]
-
A.
firstDeploymentContext
chosen
Indicates the context, environment, or situation in which something (typically a system, product, or capability) is initially deployed or put into operational use.
-
B.
firstLargeDeployment
Indicates that this is the initial instance in which something is deployed at a large or significant scale.
-
C.
firstDeploymentPlatform
Indicates the platform on which something (such as a product, service, or software) was initially deployed or launched.
-
D.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
E.
deploymentOption
Indicates the available or chosen way in which something (such as a system, service, or component) can be deployed or made operational.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.