Triple

T11190905
Position Surface form Disambiguated ID Type / Status
Subject Lismore Court House E264794 entity
Predicate hasCulturalValueFor P958 FINISHED
Object local community of Lismore 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: local community of Lismore | Statement: [Lismore Court House, hasCulturalValueFor, local community of Lismore]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCulturalValueFor
Context triple: [Lismore Court House, hasCulturalValueFor, local community of Lismore]
  • A. hasCulturalProperty
    Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
  • B. hasCulturalSignificance
    Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
  • C. hasHeritageValueFor
    Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
  • D. hasCulturalSignificanceFor chosen
    Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
  • E. isCulturalSignificance
    Indicates that something holds notable meaning, value, or influence within a particular culture or cultural context.
  • 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8af18e4819091811bca657c9cb0 completed April 9, 2026, 5:58 p.m.
PD Predicate disambiguation batch_69d75cf4461c8190af84060f7db83211 completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:29 p.m.