Triple

T19315638
Position Surface form Disambiguated ID Type / Status
Subject Ropar E483089 entity
Predicate hasArchaeologicalSiteStatus P135560 FINISHED
Object protected 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: protected site | Statement: [Ropar, hasArchaeologicalSiteStatus, protected site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalSiteStatus
Context triple: [Ropar, hasArchaeologicalSiteStatus, protected site]
  • A. isArchaeologicalSite
    Indicates that a location or structure is recognized as an archaeological site, typically due to its historical or cultural remains of past human activity.
  • B. hasArchaeologicalSiteType
    Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
  • C. hasArchaeologicalSiteCode
    Indicates that an entity is associated with a specific archaeological site identified by a formal site code.
  • D. archaeologicalSiteStatus
    Indicates the current condition or preservation state of an archaeological site, such as whether it is intact, damaged, restored, or destroyed.
  • E. hasArchaeologicalSiteIn
    Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e60d833034819092a8414d5e0fc26e completed April 20, 2026, 11:26 a.m.
PD Predicate disambiguation batch_69e4dd0ef66881909d489d634eee817a completed April 19, 2026, 1:47 p.m.
PDg Predicate description generation batch_69e4e4709d4481908c280cdd2ac18977 completed April 19, 2026, 2:19 p.m.
Created at: April 10, 2026, 1:32 p.m.