Triple
T29399971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austral wine region |
E745607
|
entity |
| Predicate | grapeGrowingConditions |
P167145
|
FINISHED |
| Object | extreme conditions |
—
|
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: extreme conditions | Statement: [Austral wine region, grapeGrowingConditions, extreme conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeGrowingConditions Context triple: [Austral wine region, grapeGrowingConditions, extreme conditions]
-
A.
grapeGrowingInfluence
Indicates how various factors affect or shape the process and outcomes of growing grapes.
-
B.
grapeCondition
Indicates the state or quality of a grape, such as its health, ripeness, or any notable physical condition.
-
C.
grapeConditionRequired
Indicates that a specific condition or quality of grapes is required for a related process, use, or outcome.
-
D.
grapePlantingShare
Indicates the proportion or share of grape planting activity attributed to or carried out by a particular entity relative to a larger whole.
-
E.
grapeGrowingLatitudeRange
Indicates the range of latitudes within which grapes are typically grown or suitable for cultivation.
- F. None of above. chosen
Provenance (4 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a06aa2c8190aa13c6561f6838b7 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 2:49 p.m.