Triple
T16952318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NutraSweet |
E411213
|
entity |
| Predicate | introducedAsBrandFor |
P125363
|
FINISHED |
| Object | aspartame |
—
|
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: aspartame | Statement: [NutraSweet, introducedAsBrandFor, aspartame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsBrandFor Context triple: [NutraSweet, introducedAsBrandFor, aspartame]
-
A.
introducedAsBrandBy
Indicates that one entity was presented or launched to the public or a market as a brand by another entity.
-
B.
brandFounded
Indicates that a specific brand was established or created at a particular point in time or by a particular founder or entity.
-
C.
brandStatusAtIntroduction
Indicates the status or condition of a brand at the time it is first introduced to the market or public.
-
D.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.