Triple
T23184481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aceto Balsamico Tradizionale di Modena |
E579550
|
entity |
| Predicate | typicalWoodTypes |
P120646
|
FINISHED |
| Object | oak |
—
|
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: oak | Statement: [Aceto Balsamico Tradizionale di Modena, typicalWoodTypes, oak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWoodTypes Context triple: [Aceto Balsamico Tradizionale di Modena, typicalWoodTypes, oak]
-
A.
topWood
Indicates that one entity is made of or features a particular type of wood used specifically for its top surface or top section.
-
B.
woodProperty
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
C.
hasWood
chosen
Indicates that one entity possesses, contains, or is made of wood in relation to another entity or context.
-
D.
oakTypeUsed
Indicates that a particular type of oak is used in relation to another entity, such as in construction, manufacturing, or production.
-
E.
hasBodyWood
Indicates that an entity’s body is made of or primarily composed of wood.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f717d248190b2736b0789981fb2 |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.