Triple

T8916861
Position Surface form Disambiguated ID Type / Status
Subject Sumerian King List E212313 entity
Predicate reignLengthsType P86372 FINISHED
Object mythically long for antediluvian 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: mythically long for antediluvian kings | Statement: [Sumerian King List, reignLengthsType, mythically long for antediluvian kings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reignLengthsType
Context triple: [Sumerian King List, reignLengthsType, mythically long for antediluvian kings]
  • A. reignDuration
    Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
  • B. reignTo
    Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
  • C. longestReigningTitle
    Indicates that a person or entity holds the record for having possessed a particular title or position for the greatest length of time compared to all others.
  • D. ended reign start year
    Indicates the calendar year in which a ruler’s period of reign came to an end.
  • E. reignInDynasty
    Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
  • F. None of above. chosen

Provenance (4 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_69cc6610cd48819090a184c5f9465626 completed April 1, 2026, 12:25 a.m.
PD Predicate disambiguation batch_69cc5ed0ef3c81908cc69eac852ee12a completed March 31, 2026, 11:54 p.m.
PDg Predicate description generation batch_69cc600a59708190ae426044bbcd7929 completed April 1, 2026, midnight
Created at: March 30, 2026, 6:56 p.m.