Triple

T36077695
Position Surface form Disambiguated ID Type / Status
Subject Davie Yards E1043542 entity
Predicate operatedHistoricSite P59071 FINISHED
Object historic Davie shipyard 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: historic Davie shipyard | Statement: [Davie Yards, operatedHistoricSite, historic Davie shipyard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatedHistoricSite
Context triple: [Davie Yards, operatedHistoricSite, historic Davie shipyard]
  • A. servesHistoricSites
    Indicates that an entity provides services, access, or support specifically to historic sites.
  • B. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • C. stateHistoricSiteManagedBy chosen
    Indicates that a designated state historic site is administered, overseen, or operated by a particular managing organization or authority.
  • D. establishedAsStateHistoricSite
    Indicates that an entity has been officially designated and recognized as a state historic site by the relevant governmental authority.
  • E. openedAsHistoricSite
    Indicates that a place or structure was officially opened or designated for public access as a recognized historic site.
  • 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_69f76e3154908190a6f702671c2bea08 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a019b8995dc819088727aa023beadce completed May 11, 2026, 9:04 a.m.
PD Predicate disambiguation batch_6a01961bb748819096a941f1b5443908 completed May 11, 2026, 8:40 a.m.
Created at: May 3, 2026, 4:08 p.m.