Triple
T24611264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monferrato of the Infernot |
E609119
|
entity |
| Predicate | traditionalUseOfInfernot |
P6999
|
FINISHED |
| Object | storing bottled wine |
—
|
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: storing bottled wine | Statement: [Monferrato of the Infernot, traditionalUseOfInfernot, storing bottled wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalUseOfInfernot Context triple: [Monferrato of the Infernot, traditionalUseOfInfernot, storing bottled wine]
-
A.
traditionalUse
chosen
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
B.
traditionalUseDomain
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
-
C.
traditionalUseRegion
Indicates the geographic region where something has been traditionally used or practiced.
-
D.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
E.
languageOfTraditionalUse
Indicates the language traditionally used or associated with a given entity, such as a work, practice, or community.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.