Triple
T12908969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pineapple Passionfruit Refresher |
E308800
|
entity |
| Predicate | secondaryTaste |
P104049
|
FINISHED |
| Object | tangy |
—
|
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: tangy | Statement: [Pineapple Passionfruit Refresher, secondaryTaste, tangy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTaste Context triple: [Pineapple Passionfruit Refresher, secondaryTaste, tangy]
-
A.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
B.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
-
C.
secondaryGrape
Indicates that one grape variety serves as a secondary or supporting component in a wine blend relative to the primary grape.
-
D.
secondaryCup
Indicates that one cup serves as a secondary or backup cup in relation to a primary cup.
-
E.
hasSecondaryFlavor
chosen
Indicates that an entity possesses an additional, subordinate flavor characteristic beyond its primary flavor.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719e584c81909be1ac1366effca0 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.