Triple

T8643528
Position Surface form Disambiguated ID Type / Status
Subject Serhedi E204713 entity
Predicate hasNameInEnglish P3437 FINISHED
Object Serhedi E204713 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: Serhedi | Statement: [Serhedi, hasNameInEnglish, Serhedi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Serhedi
Context triple: [Serhedi, hasNameInEnglish, Serhedi]
  • A. Serhedi chosen
    Serhedi is a regional dialect of Kurmanji Kurdish spoken in parts of the Kurdish-inhabited areas of the Middle East.
  • B. Serdi
    The Serdi were an ancient Thracian tribe that inhabited the region around present-day Sofia, Bulgaria, giving their name to the Roman city of Serdica.
  • C. Le Sépey
    Le Sépey is a small village in the canton of Vaud, Switzerland, situated in the Alps and serving as a local stop on the regional railway network.
  • D. Ercsi
    Ercsi is a small town in central Hungary situated along the Danube River in Fejér County.
  • E. Hernici
    The Hernici were an ancient Italic tribe of central Italy, known for their early alliance and later conflicts with the expanding Roman Republic.
  • 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_69ca834ca1c88190a11ffb0200342fac completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc4798852881909c03c5eadf805e49 completed March 31, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69cebc42922c819099a464d2e347dec4 completed April 2, 2026, 6:58 p.m.
Created at: March 30, 2026, 6:28 p.m.