Triple

T2896436
Position Surface form Disambiguated ID Type / Status
Subject John Hancock Tower, Boston E63949 entity
Predicate engineeringRemedy P4524 FINISHED
Object replacement and redesign of glass panels 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: replacement and redesign of glass panels | Statement: [John Hancock Tower, Boston, engineeringRemedy, replacement and redesign of glass panels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: engineeringRemedy
Context triple: [John Hancock Tower, Boston, engineeringRemedy, replacement and redesign of glass panels]
  • A. remedy chosen
    Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
  • B. engineeringFeature
    Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
  • C. engine
    Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
  • D. repairedIn
    Indicates that an item or object underwent repair within a specified location or during a particular time period.
  • E. laterEngineer
    Indicates that one entity becomes an engineer at a later time than another entity.
  • 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_69ab4c45822c8190830c5f2bb97bcfd0 completed March 6, 2026, 9:51 p.m.
NER Named-entity recognition batch_69abe08c85c48190bd8c0f6680fca0c8 completed March 7, 2026, 8:23 a.m.
PD Predicate disambiguation batch_69abdd17bcdc8190aa47274a50ba4ad4 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:08 p.m.