Triple
T31699711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irpinia DOC |
E809017
|
entity |
| Predicate | hasSubstyles |
P3485
|
FINISHED |
| Object | Irpinia Aglianico DOC |
—
|
NE NERFINISHED |
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: Irpinia Aglianico DOC | Statement: [Irpinia DOC, hasSubstyles, Irpinia Aglianico DOC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubstyles Context triple: [Irpinia DOC, hasSubstyles, Irpinia Aglianico DOC]
-
A.
hasSubstyle
chosen
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
-
B.
hasSubregionStyle
Indicates a stylistic relationship in which one region exhibits a specific style that is characteristic of a subregion within it.
-
C.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
D.
hasRuleStyle
Indicates that an entity is associated with a particular rule-based style or formatting specification.
-
E.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: April 30, 2026, 11:11 p.m.