Triple
T1931482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riesling |
E40954
|
entity |
| Predicate | sugarLevelRange |
P13474
|
FINISHED |
| Object | dry to lusciously sweet |
—
|
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: dry to lusciously sweet | Statement: [Riesling, sugarLevelRange, dry to lusciously sweet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sugarLevelRange Context triple: [Riesling, sugarLevelRange, dry to lusciously sweet]
-
A.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
hasSugarContent
Indicates that one entity possesses or contains a specified amount or level of sugar.
-
C.
acidityLevel
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
D.
hasSalinityRange
Indicates the range of salinity values within which something (such as a substance, environment, or organism) is present, applicable, or able to function.
-
E.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb297ec2c819092ad62d72005223d |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.