Triple
T23663633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontefract cake |
E584516
|
entity |
| Predicate | hasFlavourProfile |
P69349
|
FINISHED |
| Object | intense liquorice |
—
|
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: intense liquorice | Statement: [Pontefract cake, hasFlavourProfile, intense liquorice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlavourProfile Context triple: [Pontefract cake, hasFlavourProfile, intense liquorice]
-
A.
hasFlavorContent
Indicates that something possesses or contains a particular flavor or set of flavor characteristics.
-
B.
hasFlavorType
Indicates that an entity possesses or is characterized by a particular type or category of flavor.
-
C.
intendedFlavorProfile
Indicates the flavor characteristics that something is designed or planned to have, rather than what it actually tastes like.
-
D.
hasTastingProfile
chosen
Indicates that an entity possesses a specific flavor or sensory profile, typically describing its characteristic tastes and aromas.
-
E.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to another entity.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40a1284819087cd29c9c390549d |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.