Triple
T244749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinot Noir |
E5011
|
entity |
| Predicate | typicalAlcoholRange |
P2071
|
FINISHED |
| Object | medium |
—
|
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: medium | Statement: [Pinot Noir, typicalAlcoholRange, medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAlcoholRange Context triple: [Pinot Noir, typicalAlcoholRange, medium]
-
A.
alcoholLevel
chosen
Indicates the measured concentration or amount of alcohol present in an entity (such as a person, substance, or environment).
-
B.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
-
C.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
D.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
E.
tanninLevel
Indicates the degree or intensity of tannins present in or associated with something, typically a beverage like wine or tea.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.