Triple

T13646958
Position Surface form Disambiguated ID Type / Status
Subject Herzegovina E326127 entity
Predicate hasCity P316 FINISHED
Object Jablanica E629639 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: Jablanica | Statement: [Herzegovina, hasCity, Jablanica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jablanica
Context triple: [Herzegovina, hasCity, Jablanica]
  • A. Jablanica chosen
    Jablanica is a town in Bosnia and Herzegovina known for its location in the Neretva River valley and its historical World War II railway bridge.
  • B. Mladenovac
    Mladenovac is a suburban municipality and town located in the southern part of the City of Belgrade, Serbia.
  • C. Zvornik
    Zvornik is a historic town and municipality in northeastern Bosnia and Herzegovina, situated on the banks of the Drina River near the border with Serbia.
  • D. Doboj
    Doboj is a city in northern Bosnia and Herzegovina known as a key transport hub and strategic crossroads on the Bosna River.
  • E. Čukarica
    Čukarica is a municipality of Belgrade known for its mix of urban neighborhoods, industrial zones, and green areas along the Sava River.
  • 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_69d8076beddc8190a53156f5bea77f5e completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc6073e888190965456a639839749 completed April 12, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6471ba348190a0cd1745daff6114 completed May 8, 2026, 4:20 a.m.
Created at: April 9, 2026, 9:52 p.m.