Triple

T8628958
Position Surface form Disambiguated ID Type / Status
Subject Moskovsky District of Saint Petersburg E204351 entity
Predicate hasCharacteristicArchitecture P24956 FINISHED
Object Soviet-era 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: Soviet-era architecture | Statement: [Moskovsky District of Saint Petersburg, hasCharacteristicArchitecture, Soviet-era architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicArchitecture
Context triple: [Moskovsky District of Saint Petersburg, hasCharacteristicArchitecture, Soviet-era architecture]
  • A. hasArchitectureBy
    Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
  • B. usesArchitecture chosen
    Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
  • C. hasSubArchitecture
    Indicates that one architectural component or structure is a subordinate or constituent part of a larger overarching architecture.
  • D. hasBusArchitecture
    Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design or operation.
  • E. usesArchitectureComponent
    Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
  • 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_69ca834a4ea0819094970dceb9e389f3 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5730309081909a9a0256c9bf5f8f completed March 31, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69cc455906f8819082edd79cb4a1cf28 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:27 p.m.