Triple

T16799928
Position Surface form Disambiguated ID Type / Status
Subject Saxon Ore Mountain mining region E408328 entity
Predicate hasImportantTown P14082 FINISHED
Object Sayda E709505 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: Sayda | Statement: [Saxon Ore Mountain mining region, hasImportantTown, Sayda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sayda
Context triple: [Saxon Ore Mountain mining region, hasImportantTown, Sayda]
  • A. Sayda chosen
    Sayda is a small town in the Free State of Saxony in eastern Germany, known for its location in the Ore Mountains near the Czech border.
  • B. Bayda
    Bayda is a city in eastern Libya that has served as a significant political center, including as a meeting place for the Tobruk-based House of Representatives.
  • C. Senaya
    Senaya is a modern Eastern Aramaic dialect traditionally spoken by the Christian community from Sanandaj in western Iran.
  • D. Eldaah
    Eldaah is a minor biblical figure listed in the Hebrew Bible as one of the descendants of Abraham through his wife Keturah.
  • E. Salayea
    Salayea is a town in northwestern Liberia located within Lofa County.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2acd3548190a5f6ce7d1cf74117 completed April 18, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00ab1299ac81908e9f1eebc3424bb9 completed May 10, 2026, 3:58 p.m.
Created at: April 10, 2026, 5:22 a.m.