Triple

T8916812
Position Surface form Disambiguated ID Type / Status
Subject Sumerian King List E212313 entity
Predicate earliestCompilationDate P35832 FINISHED
Object early second millennium BCE 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: early second millennium BCE | Statement: [Sumerian King List, earliestCompilationDate, early second millennium BCE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: earliestCompilationDate
Context triple: [Sumerian King List, earliestCompilationDate, early second millennium BCE]
  • A. earliestVersionDate chosen
    Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
  • B. earliestFabricDate
    Indicates the earliest date at which the fabric (or material) associated with an entity was created or first produced.
  • C. earliestDate
    Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
  • D. firstVersionYear
    Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
  • E. earliestStrataDate
    Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
  • 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_69cc6610cd48819090a184c5f9465626 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.