Triple
T35988279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pouilly-Fumé wine |
E1040770
|
entity |
| Predicate | bestConsumedWhen |
P150927
|
FINISHED |
| Object | young |
—
|
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: young | Statement: [Pouilly-Fumé wine, bestConsumedWhen, young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestConsumedWhen Context triple: [Pouilly-Fumé wine, bestConsumedWhen, young]
-
A.
consumedAfter
Indicates that one item is consumed only after another specified item has been consumed.
-
B.
consumedFor
Indicates that one entity is used up, spent, or depleted in order to produce, enable, or obtain another entity.
-
C.
consumptionWindow
chosen
Indicates the time period or conditions within which a resource, product, or content is intended or allowed to be used or consumed.
-
D.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
E.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.