Triple

T5685382
Position Surface form Disambiguated ID Type / Status
Subject Meriç Bridge E125300 entity
Predicate locatedIn P40 FINISHED
Object Edirne E19465 NE 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: Edirne | Statement: [Meriç Bridge, locatedIn, Edirne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edirne
Context triple: [Meriç Bridge, locatedIn, Edirne]
  • A. Edirne chosen
    Edirne is a historic city in northwestern Turkey that served as an early capital of the Ottoman Empire and is renowned for its Ottoman-era architecture, including the Selimiye Mosque.
  • B. Kırklareli
    Kırklareli is a city in northwestern Turkey known for its location near the Bulgarian border, agricultural economy, and historical Ottoman-era architecture.
  • C. Ardahan
    Ardahan is a town in northeastern Turkey that serves as the capital of Ardahan Province near the border with Georgia.
  • D. Shumen
    Shumen is a city in northeastern Bulgaria known for its historical significance, including nearby medieval capitals and the Monument to 1300 Years of Bulgaria.
  • E. Vidin
    Vidin is a historic city and river port in northwestern Bulgaria on the Danube, known for its medieval fortress and role as a regional center during the Second Bulgarian Empire.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c0082a884c8190a79001bae658941f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c023ba52b48190b94f8a3ecff61eb4 completed March 22, 2026, 5:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69c07dd1758c8190ad92f250e5927c0b completed March 22, 2026, 11:40 p.m.
Created at: March 22, 2026, 3:44 p.m.