Triple

T35074412
Position Surface form Disambiguated ID Type / Status
Subject Box House E1011970 entity
Predicate hasTypicalFacade P31480 FINISHED
Object symmetrical front elevation 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: symmetrical front elevation | Statement: [Box House, hasTypicalFacade, symmetrical front elevation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalFacade
Context triple: [Box House, hasTypicalFacade, symmetrical front elevation]
  • A. hasFacadeSystem
    Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
  • B. hasFacadeBy
    Indicates that one entity’s façade (front-facing exterior surface) is designed, created, or provided by another entity.
  • C. facadeFeature chosen
    Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
  • D. hasTypicalFrontage
    Indicates that something normally faces or fronts onto something else, such as a property having its usual frontage on a particular street or area.
  • E. facadePreserved
    Indicates that the external front or face of a structure has been maintained or kept intact, typically while other parts may have been altered or redeveloped.
  • 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_69f76dd193108190af2528186f25b72a completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff5b233e9c8190adc06cca0758986b completed May 9, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69ff5a5682108190a006b23c4fcdcc7c completed May 9, 2026, 4:01 p.m.
Created at: May 3, 2026, 4:01 p.m.