Triple
T34689059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cava DO |
E890834
|
entity |
| Predicate | authorizedRegion |
P103731
|
FINISHED |
| Object | Catalonia |
—
|
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: Catalonia | Statement: [Cava DO, authorizedRegion, Catalonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedRegion Context triple: [Cava DO, authorizedRegion, Catalonia]
-
A.
authorizedInRegion
chosen
Indicates that an entity has official permission or legal authority to operate, act, or be valid within a specified geographic or administrative region.
-
B.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
C.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
D.
suppliedRegion
Indicates that one entity serves as the geographic or administrative region from which another entity receives its supply or resources.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 1, 2026, 2:05 a.m.