Triple
T29669999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encruzado |
E750640
|
entity |
| Predicate | vineyardSoilPreference |
P167145
|
FINISHED |
| Object | granite soils |
—
|
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: granite soils | Statement: [Encruzado, vineyardSoilPreference, granite soils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vineyardSoilPreference Context triple: [Encruzado, vineyardSoilPreference, granite soils]
-
A.
viticulturalCharacteristic
Indicates a relationship where a specific trait, quality, or property is attributed to viticulture or grape-growing practices.
-
B.
viticulturalFeature
Indicates a characteristic, condition, or attribute specifically related to grape growing or vineyard cultivation.
-
C.
viticulturalFocus
Indicates a focus on or specialization in viticulture, i.e., activities, practices, or interests centered on grape growing and vineyard management.
-
D.
grapeGrowingConditions
chosen
Indicates the environmental and cultivation conditions under which grapes are grown.
-
E.
viticulturalClimate
Indicates the type of climate conditions relevant to grape growing and wine production that characterize a given region or area.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f671c69b348190807d83fe1f81946f |
completed | May 2, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:04 p.m.