Triple
T15880474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fyffes |
E385062
|
entity |
| Predicate | brandIntroduced |
P5261
|
FINISHED |
| Object | Fyffes brand |
—
|
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: Fyffes brand | Statement: [Fyffes, brandIntroduced, Fyffes brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandIntroduced Context triple: [Fyffes, brandIntroduced, Fyffes brand]
-
A.
introducedAsBrandBy
chosen
Indicates that one entity was presented or launched to the public or a market as a brand by another entity.
-
B.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
C.
brandFounded
Indicates that a specific brand was established or created at a particular point in time or by a particular founder or entity.
-
D.
introducedByProductLine
Indicates that one product line is responsible for introducing, launching, or bringing another product, feature, or offering into the market or portfolio.
-
E.
brandStatusAtIntroduction
Indicates the status or condition of a brand at the time it is first introduced to the market or public.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.