Triple

T33887634
Position Surface form Disambiguated ID Type / Status
Subject Kaan dynasty E868670 entity
Predicate evidenceSource P140693 FINISHED
Object epigraphic decipherment of Maya inscriptions 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: epigraphic decipherment of Maya inscriptions | Statement: [Kaan dynasty, evidenceSource, epigraphic decipherment of Maya inscriptions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: evidenceSource
Context triple: [Kaan dynasty, evidenceSource, epigraphic decipherment of Maya inscriptions]
  • A. evidenceCited chosen
    Indicates that one entity is used as supporting evidence or citation for the claims or content of another entity.
  • B. editorialSource
    Indicates that one entity serves as the editorial origin, provider, or authority for the content or information associated with another entity.
  • C. providesEvidenceFor
    Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
  • D. documentSource
    Indicates that one entity serves as the origin, provider, or provenance source for a given document.
  • E. authorshipEvidence
    Indicates evidence or justification supporting a claim that one entity is the author or creator of another.
  • 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_69f34996761c8190864e42f7c9cf215b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:48 a.m.