Triple
T16496414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERES |
E400694
|
entity |
| Predicate | firstLaunchedOn |
P7203
|
FINISHED |
| Object | 1997-11-27 |
—
|
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: 1997-11-27 | Statement: [CERES, firstLaunchedOn, 1997-11-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunchedOn Context triple: [CERES, firstLaunchedOn, 1997-11-27]
-
A.
firstSuccessfulLaunchDate
chosen
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
firstBetaReleaseDate
Indicates the calendar date on which the first beta version of something was released.
-
D.
firstShortReleaseDate
Indicates the earliest (first) date on which a short version or short-format release of something became publicly available.
-
E.
firstShippedOn
Indicates the date on which something was initially shipped or dispatched for the first time.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e332c1c8190888a042d0192233a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.