Triple
T476202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Webb Space Telescope |
E9066
|
entity |
| Predicate | originalPlannedLaunchYear |
P14322
|
FINISHED |
| Object | around 2007 |
—
|
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: around 2007 | Statement: [James Webb Space Telescope, originalPlannedLaunchYear, around 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlannedLaunchYear Context triple: [James Webb Space Telescope, originalPlannedLaunchYear, around 2007]
-
A.
seventhPlanStartYear
Indicates the calendar year in which the seventh plan in a sequence officially begins.
-
B.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
C.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
D.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
E.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03b5e5081908ee3dba9d19a6871 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef06d2fc8190b379d575215a8518 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.