Triple
T17604300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscadinia |
E428785
|
entity |
| Predicate | hasBerryFlavorProfile |
P69349
|
FINISHED |
| Object | strong musky aroma |
—
|
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: strong musky aroma | Statement: [Muscadinia, hasBerryFlavorProfile, strong musky aroma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBerryFlavorProfile Context triple: [Muscadinia, hasBerryFlavorProfile, strong musky aroma]
-
A.
hasTastingProfile
chosen
Indicates that an entity possesses a specific flavor or sensory profile, typically describing its characteristic tastes and aromas.
-
B.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to another entity.
-
C.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
D.
hasVarietyOfFlavors
Indicates that one entity offers or contains multiple distinct flavors or taste options.
-
E.
hasFlavorType
Indicates that an entity possesses or is characterized by a particular type or category of 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4b4ee88190827ea28b99ca6f33 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.