Triple
T2735453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côte de Beaune-Villages AOC |
E60619
|
entity |
| Predicate | typicalProfile |
P41733
|
FINISHED |
| Object | elegant |
—
|
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: elegant | Statement: [Côte de Beaune-Villages AOC, typicalProfile, elegant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProfile Context triple: [Côte de Beaune-Villages AOC, typicalProfile, elegant]
-
A.
typicalPlayerProfile
Indicates the usual or characteristic attributes, behaviors, or demographics associated with a representative player in a given context.
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
E.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb1022488190af84e536946b2e37 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd968b2148190929af432c9d8001f |
completed | March 7, 2026, 7:53 a.m. |
Created at: March 6, 2026, 9:56 p.m.