Triple
T33848189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meursault hillside |
E867538
|
entity |
| Predicate | terroirComponent |
P177784
|
FINISHED |
| Object | soil |
—
|
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: soil | Statement: [Meursault hillside, terroirComponent, soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terroirComponent Context triple: [Meursault hillside, terroirComponent, soil]
-
A.
terroirDriven
Indicates that something, typically a product like wine or food, is strongly shaped or characterized by the specific environmental conditions and place where it originates.
-
B.
viticulturalCharacteristic
Indicates a relationship where a specific trait, quality, or property is attributed to viticulture or grape-growing practices.
-
C.
viticulturalFeature
Indicates a characteristic, condition, or attribute specifically related to grape growing or vineyard cultivation.
-
D.
traditionalVineyardArea
Indicates the area of land that is used as a traditional vineyard, typically cultivated with long-established grape-growing practices.
-
E.
cultivatedBy
Indicates that something (such as land, crops, or plants) is grown, tended, or developed through the efforts or care of a particular agent.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.