Triple

T3943555
Position Surface form Disambiguated ID Type / Status
Subject Thysdrus E92090 entity
Predicate amphitheatreUNESCOInscriptionYear P963 FINISHED
Object 1979 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: 1979 | Statement: [Thysdrus, amphitheatreUNESCOInscriptionYear, 1979]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: amphitheatreUNESCOInscriptionYear
Context triple: [Thysdrus, amphitheatreUNESCOInscriptionYear, 1979]
  • A. amphitheatreInstanceOf
    Indicates that an entity is classified as, or is an instance of, an amphitheatre.
  • B. archaeologicalSiteIncludes
    Indicates that an archaeological site contains, encompasses, or includes a specified feature, structure, artifact collection, or sub-area as part of its extent or composition.
  • C. majorInscriptionSite
    Indicates that a location serves as a primary or significant site where inscriptions are prominently found or produced.
  • D. UNESCOWorldHeritageDesignationYear chosen
    Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
  • E. notableArchaeologicalSite
    Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
  • 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_69aed965502c8190904ebad1203a4ae8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef1515c688190a38332aedeed8a76 completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee764235081909309b3c982f322a9 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:24 p.m.