Triple

T29254886
Position Surface form Disambiguated ID Type / Status
Subject Tipaza District E741676 entity
Predicate hasHeritageSiteIn P2499 FINISHED
Object Tipaza archaeological site NE NERFINISHED

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: Tipaza archaeological site | Statement: [Tipaza District, hasHeritageSiteIn, Tipaza archaeological site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHeritageSiteIn
Context triple: [Tipaza District, hasHeritageSiteIn, Tipaza archaeological site]
  • A. hasArchaeologicalSiteIn
    Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
  • B. hasArchaeologicalSitesFrom
    Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
  • C. hasWorldHeritageSite chosen
    Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
  • D. hasHeritageOfSite
    Indicates that a site possesses or is associated with a particular heritage designation, tradition, or cultural-historical value.
  • E. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • 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_69f0911eba2c8190b07cd2fdf91422c9 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f7675b12848190a3569cfda29c5b0e completed May 3, 2026, 3:18 p.m.
PD Predicate disambiguation batch_69f762f4b59481909f70074f11825bfb completed May 3, 2026, 3 p.m.
Created at: April 28, 2026, 12:36 p.m.