Triple
T21192617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i-mode |
E522248
|
entity |
| Predicate | commercialLaunchDate |
P123703
|
FINISHED |
| Object | 1999-02-22 |
—
|
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: 1999-02-22 | Statement: [i-mode, commercialLaunchDate, 1999-02-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialLaunchDate Context triple: [i-mode, commercialLaunchDate, 1999-02-22]
-
A.
commercialLaunchYear
Indicates the calendar year in which something was first made commercially available or launched to the market.
-
B.
commercialLaunchFirst
Indicates that this event marks the first commercial launch associated with the subject entity.
-
C.
yearOfLaunch
Indicates the specific calendar year in which an entity (such as a product, mission, or project) was first launched or released.
-
D.
firstCommercialLaunchDate
chosen
Indicates the calendar date on which an entity’s product, service, or operation was first made commercially available to the public.
-
E.
commercialLaunchProvider
Indicates that an entity serves as the organization responsible for providing launch services for a commercial space mission or payload.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73338dbe881908360dedad65c964b |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.