Triple

T6355106
Position Surface form Disambiguated ID Type / Status
Subject State of Lu E142969 entity
Predicate importantClan P1915 FINISHED
Object Shusun clan E587224 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: Shusun clan | Statement: [State of Lu, importantClan, Shusun clan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shusun clan
Context triple: [State of Lu, importantClan, Shusun clan]
  • A. Mengsun clan
    The Mengsun clan was one of the prominent aristocratic lineages in the ancient Chinese State of Lu, influential in its political and social affairs.
  • B. Ji clan
    The Ji clan was one of the three powerful aristocratic lineages that dominated the politics of the ancient Chinese State of Lu during the Spring and Autumn period.
  • C. Naya clan
    The Naya clan is an ancient Jain lineage traditionally associated with the family background of Mahavira, the 24th Tirthankara of Jainism.
  • D. Javanshir clan
    The Javanshir clan was a prominent Azerbaijani noble family that played a significant political and military role in the Karabakh region.
  • E. Jisun clan chosen
    The Jisun clan was one of the three powerful aristocratic lineages that dominated the politics of the ancient Chinese State of Lu during the Spring and Autumn period.
  • 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_69c008d6dcbc8190aa1c2f1fd8916b42 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067e22c00819089bc68efb85bc2c8 completed March 22, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6386784008190b0ac82804a4ee30e completed March 27, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:31 p.m.