Triple

T8916152
Position Surface form Disambiguated ID Type / Status
Subject mixed constitution (Sparta) E212300 entity
Predicate hasCheckOnGerousia P2945 FINISHED
Object kings 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: kings | Statement: [mixed constitution (Sparta), hasCheckOnGerousia, kings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCheckOnGerousia
Context triple: [mixed constitution (Sparta), hasCheckOnGerousia, kings]
  • A. hasJurors
    Indicates that one entity serves as or includes jurors in relation to another entity, typically in the context of a legal case or proceeding.
  • B. hasPolity
    Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
  • C. heldCouncil
    Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
  • D. hasCheckAndBalanceWith chosen
    Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
  • E. hasGeneralAssembly
    Indicates that an entity possesses or is associated with a general assembly as its formal deliberative or decision-making body.
  • 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_69ca8393b1808190bd4336787ffa2c40 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc660f6a088190b0af829ea809d8ad completed April 1, 2026, 12:25 a.m.
PD Predicate disambiguation batch_69cc5ed0ef3c81908cc69eac852ee12a completed March 31, 2026, 11:54 p.m.
Created at: March 30, 2026, 6:56 p.m.