Triple
T25373976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graciano |
E633007
|
entity |
| Predicate | authorizedInDO |
P82480
|
FINISHED |
| Object | Rioja DOCa |
—
|
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: Rioja DOCa | Statement: [Graciano, authorizedInDO, Rioja DOCa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedInDO Context triple: [Graciano, authorizedInDO, Rioja DOCa]
-
A.
authorizedIn
chosen
Indicates that an entity has been granted official permission or legal authority to act, operate, or be valid within a specified context, domain, or jurisdiction.
-
B.
authorizedOn
Indicates that an entity has been granted official permission or rights to act, access, or operate on a specified object, resource, or context.
-
C.
canAuthorize
Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
-
D.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
E.
authorizedFrom
Indicates that permission, approval, or legal authority for an action or state originates from a specified source.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 1:38 p.m.