Triple

T17892411
Position Surface form Disambiguated ID Type / Status
Subject Sanjar E447354 entity
Predicate givenName P17 FINISHED
Object Sanjar NE NERFINISHED

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: Sanjar | Statement: [Sanjar, givenName, Sanjar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sanjar
Context triple: [Sanjar, givenName, Sanjar]
  • A. Sanjar chosen
    Sanjar was a prominent 12th-century Seljuk ruler who governed the eastern provinces of the empire and is often regarded as its last great sultan.
  • B. Qalat
    Qalat is a key urban center and provincial capital in southern Afghanistan, known for its strategic location and historical fortifications.
  • C. Jahanabad
    Jahanabad is a locality that forms one of the neighborhoods within the town of SITE Town.
  • D. Musa Qala
    Musa Qala is a town and district center in southern Afghanistan that has been a focal point of conflict and military operations, particularly during the Afghan War.
  • E. Mahmudabad
    Mahmudabad is a coastal city in northern Iran, situated along the Caspian Sea in Mazandaran Province and known for its beaches and tourism.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49d7a855c8190b20bdbf6dcd4fd47 completed April 19, 2026, 9:16 a.m.
Created at: April 10, 2026, 10:19 a.m.