Triple
T22958447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vela nuclear test detection satellites |
E570823
|
entity |
| Predicate | launchEndDate |
P150385
|
FINISHED |
| Object | 1970-04-08 |
—
|
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: 1970-04-08 | Statement: [Vela nuclear test detection satellites, launchEndDate, 1970-04-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchEndDate Context triple: [Vela nuclear test detection satellites, launchEndDate, 1970-04-08]
-
A.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
launchPeriod
Indicates the time span during which a launch or deployment activity occurs or is valid.
-
C.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
D.
rolloutDate
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
E.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f2ce9c8190977f146771816341 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:47 p.m.