Triple
T55961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmos: A Personal Voyage |
E1106
|
entity |
| Predicate | originalReleaseStart |
P180
|
FINISHED |
| Object | 1980-09-28 |
—
|
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: 1980-09-28 | Statement: [Cosmos: A Personal Voyage, originalReleaseStart, 1980-09-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalReleaseStart Context triple: [Cosmos: A Personal Voyage, originalReleaseStart, 1980-09-28]
-
A.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
C.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
D.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
E.
beganOfficialNumberingWith
Indicates that an entity started its formal or official numbering sequence with a specified initial number or identifier.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.