Triple

T32836538
Position Surface form Disambiguated ID Type / Status
Subject Negru Vodă E839847 entity
Predicate connectsToSettlement P8239 FINISHED
Object Kardam, Bulgaria 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: Kardam, Bulgaria | Statement: [Negru Vodă, connectsToSettlement, Kardam, Bulgaria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsToSettlement
Context triple: [Negru Vodă, connectsToSettlement, Kardam, Bulgaria]
  • A. isSettlementOf
    Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
  • B. associatedWithSettlement chosen
    Indicates a relationship where an entity is linked or connected to a particular settlement, such as a town, village, or city.
  • C. isSettlement
    Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
  • D. connectsSettlementType
    Indicates that there is a relationship linking a settlement to its specific type or classification (e.g., village, town, city).
  • E. eligibleForSettlementSystem
    Indicates that an entity meets the required conditions to participate in or be processed by a particular settlement system.
  • 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_69f3493ff0888190b51e974eae2a7834 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fef5cf8da881908260ec633830375d completed May 9, 2026, 8:52 a.m.
PD Predicate disambiguation batch_69fef455e40481909861c82007b79bc0 completed May 9, 2026, 8:46 a.m.
Created at: May 1, 2026, 1:16 a.m.