Triple
T9322030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-16 ICBM |
E224290
|
entity |
| Predicate | deploymentStart |
P11880
|
FINISHED |
| Object | early 1960s |
—
|
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 1960s | Statement: [R-16 ICBM, deploymentStart, early 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentStart Context triple: [R-16 ICBM, deploymentStart, early 1960s]
-
A.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
B.
deploymentTime
chosen
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
C.
deploymentRequires
Indicates that performing a particular deployment is contingent upon the prior existence, completion, or availability of another specified resource, condition, or action.
-
D.
deploymentOption
Indicates the available or chosen way in which something (such as a system, service, or component) can be deployed or made operational.
-
E.
deploymentMechanism
Indicates the method or process by which something is deployed, delivered, or made operational in its target environment.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f2bd288190bb1556a88d9e90f3 |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.