Triple
T16138639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priorat |
E391594
|
entity |
| Predicate | recognizedAsQualityRegion |
P28748
|
FINISHED |
| Object | DOCa |
—
|
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: DOCa | Statement: [Priorat, recognizedAsQualityRegion, DOCa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsQualityRegion Context triple: [Priorat, recognizedAsQualityRegion, DOCa]
-
A.
regionQualifier
Indicates that one entity specifies or constrains the regional or geographic scope applicable to another entity.
-
B.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
C.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
D.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
E.
regionallyRecognizedAs
chosen
Indicates that an entity is acknowledged or designated under a specific name, status, or classification within a particular geographic region or locality.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a06e0988190b5cd62d422d058a2 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.