Triple
T31534978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Chapelle de La Mission Haut-Brion (second wine) |
E804579
|
entity |
| Predicate | terroirSoilType |
P1675
|
FINISHED |
| Object | gravelly 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: gravelly soils | Statement: [La Chapelle de La Mission Haut-Brion (second wine), terroirSoilType, gravelly soils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terroirSoilType Context triple: [La Chapelle de La Mission Haut-Brion (second wine), terroirSoilType, gravelly soils]
-
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.
soilOrigin
Indicates the source or provenance from which a given soil was formed or obtained.
-
C.
soilDisposition
Indicates how soil is arranged, oriented, or distributed in relation to surrounding features or conditions.
-
D.
hasSoil
chosen
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
E.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:03 p.m.