Triple
T32568643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valdepeñas |
E832444
|
entity |
| Predicate | hasDesignationOfOrigin |
P16569
|
FINISHED |
| Object | Valdepeñas DO |
—
|
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: Valdepeñas DO | Statement: [Valdepeñas, hasDesignationOfOrigin, Valdepeñas DO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignationOfOrigin Context triple: [Valdepeñas, hasDesignationOfOrigin, Valdepeñas DO]
-
A.
denominationOfOrigin
chosen
Indicates a legally recognized origin relationship where a product’s quality or characteristics are specifically attributable to being produced in a particular geographic region.
-
B.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
C.
namedAfterCountryOfOrigin
Indicates that an entity is named after the country from which it originates or was first produced.
-
D.
worldOfOrigin
Indicates the original world, realm, or universe from which an entity, character, or object originates.
-
E.
composerCountryOfOrigin
Indicates the country from which a composer originally comes or with which they are primarily culturally or nationally associated.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:03 a.m.