Triple
T34173694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Topaque |
E876608
|
entity |
| Predicate | wineLawTerm |
P38943
|
FINISHED |
| Object | Australian wine labeling term |
—
|
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: Australian wine labeling term | Statement: [Australian Topaque, wineLawTerm, Australian wine labeling term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineLawTerm Context triple: [Australian Topaque, wineLawTerm, Australian wine labeling term]
-
A.
wineLaw
chosen
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
B.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
C.
wineDenomination
Indicates that a wine is classified under a specific official denomination or appellation.
-
D.
wineDevelopment
Indicates the process or progression of how a wine changes, matures, or evolves in character over time.
-
E.
oenologicalSignificance
Indicates the relationship in which something holds importance, relevance, or notable impact within the context of wine or winemaking.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe7313c8190a4b8d08e659815c2 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.