Triple

T35472670
Position Surface form Disambiguated ID Type / Status
Subject Val do Salnés E1025243 entity
Predicate hasSubregionStatusSince P201187 FINISHED
Object creation of Rías Baixas DO 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: creation of Rías Baixas DO | Statement: [Val do Salnés, hasSubregionStatusSince, creation of Rías Baixas DO]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSubregionStatusSince
Context triple: [Val do Salnés, hasSubregionStatusSince, creation of Rías Baixas DO]
  • A. hasSubregionStatus
    Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
  • B. hasSubregionRelationWith
    Indicates a relationship where one region is a subregion or contained part of another region.
  • C. isInSubregion
    Indicates that one region or area is located within the boundaries of another, more specific subregion.
  • D. hasHistoricalCountrySubdivision
    Indicates that one entity was a territorial or administrative subdivision of a historical country.
  • E. isInFormerRegion
    Indicates that one entity is located within a geographic or administrative area that previously existed or had a different status or boundaries in the past.
  • F. None of above. chosen

Provenance (4 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_69f76dfadba0819083456aadcd6864ea completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ffdd05d1908190957deb11392f4595 completed May 10, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69ffdc0d33c881908b3483bee8a96540 completed May 10, 2026, 1:14 a.m.
PDg Predicate description generation batch_69ffdd0486e08190a0f2ff4ce0aee13b completed May 10, 2026, 1:19 a.m.
Created at: May 3, 2026, 4:04 p.m.