Triple
T2708385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auxey-Duresses |
E59797
|
entity |
| Predicate | typicalRedProfile |
P42476
|
FINISHED |
| Object | medium-bodied Pinot Noir |
—
|
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: medium-bodied Pinot Noir | Statement: [Auxey-Duresses, typicalRedProfile, medium-bodied Pinot Noir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRedProfile Context triple: [Auxey-Duresses, typicalRedProfile, medium-bodied Pinot Noir]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalColorDescription
Indicates the usual or characteristic color associated with an entity.
-
C.
typicalPlayerProfile
Indicates the usual or characteristic attributes, behaviors, or demographics associated with a representative player in a given context.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda73de1c81908f5d6b0383e23144 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:55 p.m.