Triple
T35516155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caiño Blanco |
E1026424
|
entity |
| Predicate | valuedInRegion |
P9687
|
FINISHED |
| Object | Rías Baixas |
—
|
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: Rías Baixas | Statement: [Caiño Blanco, valuedInRegion, Rías Baixas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valuedInRegion Context triple: [Caiño Blanco, valuedInRegion, Rías Baixas]
-
A.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
B.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
C.
suppliedRegion
Indicates that one entity serves as the geographic or administrative region from which another entity receives its supply or resources.
-
D.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
E.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.