Triple
T13816992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet thermonuclear weapons program |
E332044
|
entity |
| Predicate | firstTrueTwoStageTestDate |
P111606
|
FINISHED |
| Object | 1955-11-22 |
—
|
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: 1955-11-22 | Statement: [Soviet thermonuclear weapons program, firstTrueTwoStageTestDate, 1955-11-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTrueTwoStageTestDate Context triple: [Soviet thermonuclear weapons program, firstTrueTwoStageTestDate, 1955-11-22]
-
A.
firstPhaseEndDate
Indicates the date on which the first phase of a process, project, or activity is completed or scheduled to end.
-
B.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
C.
secondTestSeriesDate
Indicates the date on which the second test in a series is scheduled or took place.
-
D.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
E.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0281bb988190803ee195f430b9c8 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:12 p.m.