Triple
T37824267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contessa Entellina DOC |
E943007
|
entity |
| Predicate | usesNativeVarieties |
P189251
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Contessa Entellina DOC, usesNativeVarieties, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNativeVarieties Context triple: [Contessa Entellina DOC, usesNativeVarieties, true]
-
A.
hasNonStandardizedVarieties
Indicates that an entity possesses forms or variants that are not governed by a uniform or officially established standard.
-
B.
hasVarietyOf
Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
-
C.
usesNaturalColorVariations
Indicates that an entity employs naturally occurring differences in color, rather than artificial or uniform coloring, as part of its appearance or design.
-
D.
isPrimaryVarietyOf
Indicates that one variety is the main or principal form of another related variety or entity.
-
E.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.