Triple

T30164762
Position Surface form Disambiguated ID Type / Status
Subject City of Kesh E766764 entity
Predicate hasUncertainArchaeologicalLocation P114232 FINISHED
Object true 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: true | Statement: [City of Kesh, hasUncertainArchaeologicalLocation, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUncertainArchaeologicalLocation
Context triple: [City of Kesh, hasUncertainArchaeologicalLocation, true]
  • A. hasUncertainBurialSite
    Indicates that the location of an entity’s burial site is unknown, disputed, or not reliably established.
  • B. hasArchaeologicalCertainty
    Indicates that the relationship or claim is supported by archaeological evidence to a specified degree of confidence.
  • C. possibleArchaeologicalCorrelateLocation chosen
    Indicates that a location is a plausible archaeological site or area that may correspond to, or provide material evidence for, a particular entity or phenomenon.
  • D. hasUncertainOrigin
    Indicates that the origin or source of an entity, event, or information is unknown, unclear, or not reliably established.
  • E. hasUncertainHistoricBasis
    Indicates that the historical foundation or authenticity of the related fact, event, or relationship is doubtful, disputed, or not firmly established.
  • 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_69f2247a968881909d79c18f2bfcb275 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f71f8ee0688190bd025f27993452d3 completed May 3, 2026, 10:12 a.m.
PD Predicate disambiguation batch_69f71cc405c08190863565609a4c8499 completed May 3, 2026, 10 a.m.
Created at: April 29, 2026, 7:22 p.m.