Triple
T28034009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spätburgunder |
E708351
|
entity |
| Predicate | hasTypicalBody |
P190480
|
FINISHED |
| Object | light-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: light-bodied | Statement: [Spätburgunder, hasTypicalBody, light-bodied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBody Context triple: [Spätburgunder, hasTypicalBody, light-bodied]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
haveBody
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
-
C.
hasMainBody
Indicates that one entity serves as the primary physical or structural body of another entity.
-
D.
hasSpecialBody
Indicates that an entity possesses a distinctive or non-standard physical form or body type compared to typical instances in its category.
-
E.
hasTypicalAppearance
Indicates that an entity exhibits the standard or commonly expected visual form or look associated with its kind.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: April 27, 2026, 8:19 p.m.