Triple
T34237516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Flakes |
E878374
|
entity |
| Predicate | introducedAsProduct |
P195654
|
FINISHED |
| Object | 1906 |
—
|
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: 1906 | Statement: [Corn Flakes, introducedAsProduct, 1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsProduct Context triple: [Corn Flakes, introducedAsProduct, 1906]
-
A.
introducedInProduct
Indicates that something (such as a feature, component, or concept) first appeared or was initially made available within a particular product.
-
B.
introducedByProductLine
Indicates that one product line is responsible for introducing, launching, or bringing another product, feature, or offering into the market or portfolio.
-
C.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
D.
introducedAsBrandFor
Indicates that one entity was presented or launched to the public specifically as the brand representing another entity.
-
E.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: May 1, 2026, 1:56 a.m.