Triple
T29990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabernet Sauvignon |
E599
|
entity |
| Predicate | body |
P2067
|
FINISHED |
| Object | full-bodied |
—
|
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: full-bodied | Statement: [Cabernet Sauvignon, body, full-bodied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: body Context triple: [Cabernet Sauvignon, body, full-bodied]
-
A.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
B.
proposedByBody
Indicates that something (such as a decision, measure, or action) has been formally put forward or initiated by a specific governing or organizational body.
-
C.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
D.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
E.
title
Indicates that one entity serves as the formal name or designation of another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490d80a0819083bf604c1229e903 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486eb01881909241540dda28e1ff |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a2490c9c348190bf8536a08415b94a |
completed | Feb. 28, 2026, 1:46 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.