Triple

T30360316
Position Surface form Disambiguated ID Type / Status
Subject Third Dynasty of Kish E772263 entity
Predicate precedesInTradition P180804 FINISHED
Object Akkadian Empire NE NERFINISHED

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: Akkadian Empire | Statement: [Third Dynasty of Kish, precedesInTradition, Akkadian Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: precedesInTradition
Context triple: [Third Dynasty of Kish, precedesInTradition, Akkadian Empire]
  • A. traditionInheritedFrom
    Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
  • B. isSuccessorInTraditionTo
    Indicates that one entity follows and continues the practices, ideas, or legacy of another within a particular tradition or lineage.
  • C. mentionedInTraditionOf
    Indicates that something is referenced, recognized, or discussed within the body of beliefs, practices, or narratives of a particular tradition.
  • D. foundedInTradition
    Indicates that something is established, developed, or grounded within a particular tradition or set of longstanding customary practices.
  • E. mainTradition
    Indicates that one entity represents the primary or dominant tradition associated with another entity.
  • 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_69f2248c6f5c8190a6177842bf791a3c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7516d5b4081908588a6feb541f355 completed May 3, 2026, 1:45 p.m.
PD Predicate disambiguation batch_69f74d40ebb081909daf60623e38f41d completed May 3, 2026, 1:27 p.m.
PDg Predicate description generation batch_69f7516c538481908c6e55cf76add098 completed May 3, 2026, 1:45 p.m.
Created at: April 29, 2026, 7:57 p.m.