Triple
T27298643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charmes-Chambertin |
E688837
|
entity |
| Predicate | agingProfile |
P74136
|
FINISHED |
| Object | develops complexity with bottle age |
—
|
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: develops complexity with bottle age | Statement: [Charmes-Chambertin, agingProfile, develops complexity with bottle age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingProfile Context triple: [Charmes-Chambertin, agingProfile, develops complexity with bottle age]
-
A.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
B.
agingCommon
chosen
Indicates that the entities share a common or typical pattern, process, or characteristic related to aging.
-
C.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
D.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
-
E.
typicalHeadProfile
Indicates that an entity has a head shape or outline that conforms to a standard or commonly observed profile for its type.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62782b9048190b942a03b3518b863 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:20 a.m.