Triple

T10776086
Position Surface form Disambiguated ID Type / Status
Subject Foča massacres E254200 entity
Predicate location P40 FINISHED
Object Foča E629800 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: Foča | Statement: [Foča massacres, location, Foča]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Foča
Context triple: [Foča massacres, location, Foča]
  • A. Foča chosen
    Foča is a historic town in southeastern Bosnia and Herzegovina, known for its scenic setting near the Drina River and its significant role in regional history.
  • B. Fažana
    Fažana is a coastal town in Croatia’s Istria region, known for its fishing heritage, tourism, and historical ties to the Istriot language.
  • C. Fadicca
    Fadicca is an alternative name for the Mahas, a Nubian ethnic group traditionally living along the Nile in northern Sudan and southern Egypt.
  • D. Fussa
    Fussa is a city in western Tokyo, Japan, known for hosting Yokota Air Base and various Japan Air Self-Defense Force facilities.
  • E. Žepa
    Žepa is a small town in eastern Bosnia and Herzegovina that became known as a UN-declared "safe area" and site of a tragic episode during the Bosnian War.
  • 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_69d6aa609f008190a294200aefcb7bd5 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7329d8c908190bddad40685133ea1 completed April 9, 2026, 5:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69de238ff88881908676d38dca041cb4 completed April 14, 2026, 11:22 a.m.
Created at: April 8, 2026, 9:16 p.m.