Triple

T34859496
Position Surface form Disambiguated ID Type / Status
Subject tripoint of Bulgaria–Greece–Turkey E1004825 entity
Predicate countrySubdivisionTurkey P203473 FINISHED
Object Edirne Province 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: Edirne Province | Statement: [tripoint of Bulgaria–Greece–Turkey, countrySubdivisionTurkey, Edirne Province]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countrySubdivisionTurkey
Context triple: [tripoint of Bulgaria–Greece–Turkey, countrySubdivisionTurkey, Edirne Province]
  • A. nearCityInTurkey
    Indicates that one entity is located close to, but not necessarily within, a specified city in Turkey.
  • B. adjacentProvince_Turkey
    Indicates that one Turkish province is geographically adjacent to (shares a border with) another Turkish province.
  • C. isInCentralTurkey
    Indicates that one entity is geographically located within the central region of Turkey.
  • D. hasPopulationRankInTurkey
    Indicates the relative position of an entity in the ordered list of populations within Turkey, such as its rank by population size compared to other entities in the country.
  • E. affectedTurkishProvince
    Indicates that a Turkish province is impacted or influenced by a specified event, condition, or entity.
  • 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_69f76dbb678081909a247b9b5e1a73ac completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a0189f3f0248190a1b018164d18e6f5 completed May 11, 2026, 7:49 a.m.
PD Predicate disambiguation batch_6a0187ee0920819097047bb55e1f9506 completed May 11, 2026, 7:40 a.m.
PDg Predicate description generation batch_6a0189f318c881909c4995203a58a097 completed May 11, 2026, 7:49 a.m.
Created at: May 3, 2026, 4 p.m.