Triple

T34312866
Position Surface form Disambiguated ID Type / Status
Subject Ihnasya el‑Medina necropolis E880499 entity
Predicate chronologicalExtent P82593 FINISHED
Object spans multiple periods of ancient Egyptian history 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: spans multiple periods of ancient Egyptian history | Statement: [Ihnasya el‑Medina necropolis, chronologicalExtent, spans multiple periods of ancient Egyptian history]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: chronologicalExtent
Context triple: [Ihnasya el‑Medina necropolis, chronologicalExtent, spans multiple periods of ancient Egyptian history]
  • A. chronologicalRange chosen
    Indicates the temporal span or period over which something occurs, is valid, or is relevant.
  • B. chronologyStart
    Indicates the point in time at which a sequence, event, or temporal record begins.
  • C. chronologyOf
    Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
  • D. chronologyIncludes
    Indicates that a broader chronological sequence or timeline encompasses a specific time span, event, or period as part of it.
  • E. chronologicalPoint
    Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
  • 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_69f349b8bb6c8190ad12a7957a574f04 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fdd92396788190ae1424bc1ae55844 completed May 8, 2026, 12:37 p.m.
PD Predicate disambiguation batch_69fdd678f40481909a717a2daec83b36 completed May 8, 2026, 12:26 p.m.
Created at: May 1, 2026, 1:57 a.m.