Triple

T3295620
Position Surface form Disambiguated ID Type / Status
Subject Bardiya E69207 entity
Predicate historicalControversy P42781 FINISHED
Object identity of the ruler called Smerdis LITERAL 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: identity of the ruler called Smerdis | Statement: [Bardiya, historicalControversy, identity of the ruler called Smerdis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalControversy
Context triple: [Bardiya, historicalControversy, identity of the ruler called Smerdis]
  • A. historicalIssue
    Indicates that one entity is a past or previously existing edition, version, or instance of another entity, typically within a chronological sequence.
  • B. historicallyContestedBy
    Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
  • C. controversyType chosen
    Indicates the specific kind or category of controversy associated with an entity or situation.
  • D. controversy
    Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
  • E. locationOfControversy
    Indicates the place or setting where a dispute, debate, or controversy occurs or is centered.
  • F. None of above.

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_69ad859e529c8190a404273f53cb487d completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb077c60c81909782be5202ce5a43 completed March 8, 2026, 5:23 p.m.
PD Predicate disambiguation batch_69ada42407dc81909f60d7a14e1b7934 completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:10 p.m.