Triple
T6553025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunello di Montalcino |
E151173
|
entity |
| Predicate | agingPotentialTypical |
P2072
|
FINISHED |
| Object | 10–30 years |
—
|
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: 10–30 years | Statement: [Brunello di Montalcino, agingPotentialTypical, 10–30 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingPotentialTypical Context triple: [Brunello di Montalcino, agingPotentialTypical, 10–30 years]
-
A.
agingPotential
chosen
Indicates the capacity or suitability of something to improve, develop, or remain effective over time as it ages.
-
B.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
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.
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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.