Triple

T33467111
Position Surface form Disambiguated ID Type / Status
Subject Dedumose II E857082 entity
Predicate archaeologicalRecord P176658 FINISHED
Object sparse 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: sparse | Statement: [Dedumose II, archaeologicalRecord, sparse]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: archaeologicalRecord
Context triple: [Dedumose II, archaeologicalRecord, sparse]
  • A. archaeologicalDiscipline
    Indicates that one entity is an archaeological field or subfield in which the other entity (such as a person, project, or work) is specialized or involved.
  • B. archaeologicalExcavations
    Indicates that archaeological excavations have been carried out on or are associated with the subject, typically involving systematic digging and recovery of material remains.
  • C. archaeologicalCorrelation
    Indicates a relationship where archaeological evidence from different sources or sites is shown to be systematically related, suggesting a meaningful connection or pattern between them.
  • D. archaeologyAt
    Indicates that an archaeological activity, study, or investigation is conducted at a specific location or site.
  • E. archaeologicalHorizon
    Indicates a temporal layer or phase in the archaeological record that groups artifacts and features sharing similar characteristics and dating to the same general period.
  • F. None of above. chosen

Provenance (4 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_69f34973461481909c701c98ebd75623 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e52a6d40819084472f6072c91e9f completed May 3, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69f6e3da41948190a4cfe866ce184f73 completed May 3, 2026, 5:57 a.m.
PDg Predicate description generation batch_69f6e47c13348190a10528c84a401178 completed May 3, 2026, 6 a.m.
Created at: May 1, 2026, 1:37 a.m.