Triple
T2958115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vieux Château Certan |
E79980
|
entity |
| Predicate | vineyardLocation |
P45203
|
FINISHED |
| Object | central Pomerol plateau |
—
|
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: central Pomerol plateau | Statement: [Vieux Château Certan, vineyardLocation, central Pomerol plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vineyardLocation Context triple: [Vieux Château Certan, vineyardLocation, central Pomerol plateau]
-
A.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
-
B.
neighboringVineyard
Indicates that one vineyard is located adjacent to or very close to another vineyard.
-
C.
viticulturalFeature
Indicates a characteristic, condition, or attribute specifically related to grape growing or vineyard cultivation.
-
D.
viticulturalAreaCode
Indicates the designated code that identifies the specific viticultural (wine-producing) area associated with an entity.
-
E.
viticulturalAreaDesignation
Indicates that a specific geographic area is officially designated or recognized for viticulture (grape growing and wine production).
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992b33e081909d22a19d5064c47d |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad98379fac8190a4dfe530787703c9 |
completed | March 8, 2026, 3:39 p.m. |
Created at: March 8, 2026, 2:57 p.m.