Triple
T9865993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundy AOC wines |
E239833
|
entity |
| Predicate | qualityHierarchyLevel |
P7279
|
FINISHED |
| Object | regional appellation |
—
|
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: regional appellation | Statement: [Burgundy AOC wines, qualityHierarchyLevel, regional appellation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualityHierarchyLevel Context triple: [Burgundy AOC wines, qualityHierarchyLevel, regional appellation]
-
A.
ordinationLevel
Indicates the hierarchical rank or degree of authority assigned to an entity within an ordered or structured system.
-
B.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
C.
classificationLevel
chosen
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
D.
quality
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
-
E.
hasRatingLevel
Indicates that an entity is associated with a particular rating level or score category.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d091e48190b10463562d0dc461 |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.