Triple
T7857398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Touch Cover |
E182411
|
entity |
| Predicate | marketReleaseYear |
P31245
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Touch Cover, marketReleaseYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketReleaseYear Context triple: [Touch Cover, marketReleaseYear, 2012]
-
A.
businessReleaseDate
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
-
B.
workReleaseYear
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
-
C.
brandLaunchYear
Indicates the calendar year in which a brand was first introduced or launched to the market.
-
D.
EPReleaseYear
Indicates the calendar year in which an EP (extended play recording) was officially released.
-
E.
consumerReleaseDate
chosen
Indicates the date on which a product or service becomes available for purchase or use by general consumers.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.