Triple

T1214521
Position Surface form Disambiguated ID Type / Status
Subject Pompey’s Pillar E26077 entity
Predicate archaeologicalSiteType P23168 FINISHED
Object classical archaeology site 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: classical archaeology site | Statement: [Pompey’s Pillar, archaeologicalSiteType, classical archaeology site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: archaeologicalSiteType
Context triple: [Pompey’s Pillar, archaeologicalSiteType, classical archaeology site]
  • A. hasArchaeologicalSiteType chosen
    Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
  • B. cultSite
    Indicates a location that is or was used for religious or ritual worship activities.
  • C. notableArchaeologicalSite
    Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
  • D. excavationSite
    Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
  • E. UNESCOSiteType
    Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be0370b4819093618930f4eecfcc completed March 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69a4bb62a7c08190a79dcb6ff72ac99b completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:46 p.m.