Triple

T33409639
Position Surface form Disambiguated ID Type / Status
Subject Wepwawetemsaf E855541 entity
Predicate historicalRecordType P85795 FINISHED
Object royal stela inscription 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: royal stela inscription | Statement: [Wepwawetemsaf, historicalRecordType, royal stela inscription]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRecordType
Context triple: [Wepwawetemsaf, historicalRecordType, royal stela inscription]
  • A. historicalType
    Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
  • B. historicalRecord chosen
    Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
  • C. historicalRecordStatus
    Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
  • D. hasTypeHistory
    Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
  • E. historicalNameType
    Indicates that the relationship specifies the type or category of a historical name associated with an entity.
  • 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_69f3496f04a08190804e56ac5098b8e4 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ffff262fac8190a26ed0577e1860bd completed May 10, 2026, 3:44 a.m.
PD Predicate disambiguation batch_69fffcad7d7c8190a4ad7bb35e33bb75 completed May 10, 2026, 3:34 a.m.
Created at: May 1, 2026, 1:36 a.m.