Triple

T461506
Position Surface form Disambiguated ID Type / Status
Subject Boston Landmark (some components) E7348 entity
Predicate hasSignificanceType P428 FINISHED
Object cultural significance 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: cultural significance | Statement: [Boston Landmark (some components), hasSignificanceType, cultural significance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignificanceType
Context triple: [Boston Landmark (some components), hasSignificanceType, cultural significance]
  • A. hasSign
    Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
  • B. significance chosen
    Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
  • C. hasTypeOfInsignia
    Indicates that an entity bears or is associated with a specific kind or category of insignia.
  • D. hasSignFor
    Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
  • E. hasSignificantLanguage
    Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
  • 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_69a2e7e5c5bc8190a1dc8178218fba40 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2efbed5b88190a45716812eb4cfdf completed Feb. 28, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69a2ede75b6c81908350103d21f22a03 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.