Triple

T491944
Position Surface form Disambiguated ID Type / Status
Subject Palace of Assembly, Chandigarh E10206 entity
Predicate lightingDesign P1280 FINISHED
Object use of natural light through high-level openings 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: use of natural light through high-level openings | Statement: [Palace of Assembly, Chandigarh, lightingDesign, use of natural light through high-level openings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lightingDesign
Context triple: [Palace of Assembly, Chandigarh, lightingDesign, use of natural light through high-level openings]
  • A. designLuminosity
    Indicates the specified luminosity level or brightness characteristics that something is designed or intended to have.
  • B. hasLighting chosen
    Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
  • C. lightSourceFor
    Indicates that one entity serves as the source of illumination for another entity.
  • D. led
    Indicates that one entity guided, directed, or was in charge of another entity or activity, typically over a period of time.
  • E. lightRange
    Indicates the distance or area over which a light source effectively emits or illuminates.
  • 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_69a2e847df8481909239ec08ccf1e376 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f0f959b481908f9f28fb96695924 completed Feb. 28, 2026, 1:43 p.m.
PD Predicate disambiguation batch_69a2edf7ce008190836fb6ab5ea39375 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.