Triple
T32162255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ezerjó |
E821458
|
entity |
| Predicate | traditionalVarietyOf |
P196249
|
FINISHED |
| Object | Mór wine region |
—
|
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: Mór wine region | Statement: [Ezerjó, traditionalVarietyOf, Mór wine region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalVarietyOf Context triple: [Ezerjó, traditionalVarietyOf, Mór wine region]
-
A.
traditionalVariety
chosen
Indicates that one entity is a traditional or long-established variety, type, or form of another entity.
-
B.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
C.
varietyOf
Indicates that one entity is a specific type, kind, or variant of another, more general entity.
-
D.
traditionalSee
Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
-
E.
standardVarietyBasedIn
Indicates that a standard or reference variety (such as a language or dialect) is primarily established, recognized, or centered in a particular location or region.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 1, 2026, 12:32 a.m.