Triple

T1392279
Position Surface form Disambiguated ID Type / Status
Subject Shame E29985 entity
Predicate hasCharacter P2308 FINISHED
Object Iskander Harappa E38043 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: Iskander Harappa | Statement: [Shame, hasCharacter, Iskander Harappa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iskander Harappa
Context triple: [Shame, hasCharacter, Iskander Harappa]
  • A. Dalbandin
    Dalbandin is a small town in Pakistan’s Balochistan province, known as an important stop along the Quetta–Taftan highway and for its proximity to the Chagai nuclear testing sites.
  • B. Eskandar chosen
    Eskandar is a Persian and Arabic form of the name Alexander, commonly used in historical and literary contexts to refer to Alexander the Great.
  • C. King Porus
    King Porus was an ancient Indian ruler of the Punjab region, renowned for his valiant resistance against Alexander the Great during the Battle of the Hydaspes.
  • D. Mirza
    Mirza is a historical noble title of Persian and Central Asian origin, commonly borne by princes and high-ranking members of royal and aristocratic families.
  • E. Rajasuya
    Rajasuya is an ancient Vedic royal consecration ritual performed to legitimize and exalt a king’s sovereignty and supreme status.
  • 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_69a498dc92f8819094a1108f8ac90f43 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c360a7f08190ab7e903764b06fdf completed March 1, 2026, 10:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69acde28dd888190baa4a26f96f33e0a completed March 8, 2026, 2:25 a.m.
Created at: March 1, 2026, 7:59 p.m.