Triple
T2911605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aggregat 4 |
E63693
|
entity |
| Predicate | firstSuccessfulTestLaunchDate |
P7203
|
FINISHED |
| Object | 3 October 1942 |
—
|
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: 3 October 1942 | Statement: [Aggregat 4, firstSuccessfulTestLaunchDate, 3 October 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSuccessfulTestLaunchDate Context triple: [Aggregat 4, firstSuccessfulTestLaunchDate, 3 October 1942]
-
A.
firstSuccessfulLaunchDate
chosen
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
secondSuccessfulLaunchDate
Indicates the date on which an entity’s second launch attempt was successfully completed.
-
C.
lastLaunchDate
Indicates the date on which the most recent launch event associated with an entity occurred.
-
D.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
E.
firstCrashDate
Indicates the date on which the first crash or failure event occurred for the entity in question.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.