Triple

T10290439
Position Surface form Disambiguated ID Type / Status
Subject Indre E241347 entity
Predicate containsTown P847 FINISHED
Object Issoudun E241346 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: Issoudun | Statement: [Indre, containsTown, Issoudun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Issoudun
Context triple: [Indre, containsTown, Issoudun]
  • A. Issoudun chosen
    Issoudun is a historic commune in central France known for its medieval architecture and location within the Indre department.
  • B. Hillah
    Hillah is a city in central Iraq on the Euphrates River, known as the modern settlement adjacent to the ruins of ancient Babylon.
  • C. Medeba
    Medeba is an ancient city east of the Dead Sea, known from biblical accounts and later as a significant settlement in the region of Moab.
  • D. Balad
    Balad is a town in Somalia’s Banaadir region, located north of the capital Mogadishu and known as an agricultural and trading center along the Shabelle River.
  • E. Balad
    Balad is a city in Iraq’s Salah ad Din Governorate, known for its strategic location north of Baghdad and its nearby military air base.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2d192288190a64c27a4f26b71fc completed April 7, 2026, 9:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d71d1465e88190aaa8b295df3f9c8c completed April 9, 2026, 3:29 a.m.
Created at: April 6, 2026, 11:41 a.m.