Triple

T24205755
Position Surface form Disambiguated ID Type / Status
Subject Renaissance Scotland E600099 entity
Predicate hasArchitecturalSite P155203 FINISHED
Object Stirling Castle 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: Stirling Castle | Statement: [Renaissance Scotland, hasArchitecturalSite, Stirling Castle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalSite
Context triple: [Renaissance Scotland, hasArchitecturalSite, Stirling Castle]
  • A. hasArchaeologicalSiteIn
    Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
  • B. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • C. hasArchaeologicalSiteStatus
    Indicates that an entity holds an officially recognized status or designation as an archaeological site.
  • D. hasArchaeologicalSitesFrom
    Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
  • E. 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.
  • 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_69e288ceaab88190899d0acb5931591d completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27ca63d188190add6c41929bb5cb5 completed April 29, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f1c43e55688190b55fc20274ed471c completed April 29, 2026, 8:41 a.m.
PDg Predicate description generation batch_69f1c9834064819082024233d9c6f98f completed April 29, 2026, 9:04 a.m.
Created at: April 17, 2026, 11:37 p.m.