Triple

T30360299
Position Surface form Disambiguated ID Type / Status
Subject Third Dynasty of Kish E772263 entity
Predicate hasHistoricalAttestation P116736 FINISHED
Object limited 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: limited | Statement: [Third Dynasty of Kish, hasHistoricalAttestation, limited]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalAttestation
Context triple: [Third Dynasty of Kish, hasHistoricalAttestation, limited]
  • A. hasLatestAttestation
    Indicates that an entity is associated with its most recent or up-to-date attestation record.
  • B. hasAttestation
    Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
  • C. hasAttestationStatus
    Indicates the current verification or approval state that has been assigned to something, such as whether it has been formally attested, validated, or certified.
  • D. hasLimitedAttestation chosen
    Indicates that the relationship or fact is supported by only a small number of sources, occurrences, or pieces of evidence.
  • E. hasHistorySince
    Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
  • 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_69f2248c6f5c8190a6177842bf791a3c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fdb31800508190beec15adb9bbd292 completed May 8, 2026, 9:55 a.m.
PD Predicate disambiguation batch_69fdb19c381c8190bafb2f565da097f1 completed May 8, 2026, 9:49 a.m.
Created at: April 29, 2026, 7:57 p.m.