Triple
T8673637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Demo 2 |
E205859
|
entity |
| Predicate | yearOfLaunch |
P84405
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Launch Demo 2, yearOfLaunch, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfLaunch Context triple: [Launch Demo 2, yearOfLaunch, 2021]
-
A.
launchedEndYear
Indicates the calendar year in which a launch event or activity came to an end.
-
B.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
C.
originalPlannedLaunchYear
Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
-
D.
commercialLaunchYear
Indicates the calendar year in which something was first made commercially available or launched to the market.
-
E.
firstFlagshipLaunchYear
Indicates the calendar year in which an entity’s first flagship (primary or leading) product, service, or initiative was launched.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc4ae517108190a71a86349815f4ce |
completed | March 31, 2026, 10:29 p.m. |
Created at: March 30, 2026, 6:31 p.m.