Triple

T21632263
Position Surface form Disambiguated ID Type / Status
Subject Calgary Central Library (concept involvement / competition phase) E533860 entity
Predicate hasDesignDiscipline P62830 FINISHED
Object architecture 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: architecture | Statement: [Calgary Central Library (concept involvement / competition phase), hasDesignDiscipline, architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDesignDiscipline
Context triple: [Calgary Central Library (concept involvement / competition phase), hasDesignDiscipline, architecture]
  • A. designDiscipline chosen
    Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
  • B. hasArchitecturalDiscipline
    Indicates that one entity is associated with, practices, or specializes in a particular architectural discipline or field.
  • C. hasDesignAuthority
    Indicates that one entity holds the recognized power or responsibility to make or approve design decisions affecting another entity.
  • D. hasDesignExpertise
    Indicates that one entity possesses specialized knowledge or skill in design related to another entity.
  • E. hasDesign
    Indicates that one entity possesses, embodies, or is characterized by a particular design associated with 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_69e0c465ae7481908577b7209fdb2a77 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5217952c8190910c2103fb4a27d9 completed April 27, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69e69677b9c48190bf81f795aa8ad74e completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:34 p.m.