Triple
T9288291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundy wine classification system |
E223452
|
entity |
| Predicate | ranksVineyards |
P87428
|
FINISHED |
| Object | Grand Cru vineyards |
—
|
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: Grand Cru vineyards | Statement: [Burgundy wine classification system, ranksVineyards, Grand Cru vineyards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ranksVineyards Context triple: [Burgundy wine classification system, ranksVineyards, Grand Cru vineyards]
-
A.
vineyardAreaRankInFrance
Indicates the relative position of an entity’s vineyard area compared to other vineyard areas within France, ordered by size.
-
B.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
-
C.
wineReputation
Indicates the perceived quality, prestige, or standing of a wine based on expert opinion, consumer perception, or historical recognition.
-
D.
vineyardLocation
Indicates the geographical place where a vineyard is situated or established.
-
E.
neighboringVineyard
Indicates that one vineyard is located adjacent to or very close to another vineyard.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.