Triple
T19970093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking program |
E480047
|
entity |
| Predicate | secondLaunchDate |
P7204
|
FINISHED |
| Object | 1975-09-09 |
—
|
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: 1975-09-09 | Statement: [Viking program, secondLaunchDate, 1975-09-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondLaunchDate Context triple: [Viking program, secondLaunchDate, 1975-09-09]
-
A.
secondSuccessfulLaunchDate
chosen
Indicates the date on which an entity’s second launch attempt was successfully completed.
-
B.
secondGenerationLaunch
Indicates that an entity initiates or is associated with the launch of a second-generation version of a product, system, or technology.
-
C.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
D.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
E.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc89b508190879d29bef546aac8 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.