Triple

T6266221
Position Surface form Disambiguated ID Type / Status
Subject Barcode skyline E140418 entity
Predicate hasPlanningGoal P69054 FINISHED
Object maintain views and light between buildings 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: maintain views and light between buildings | Statement: [Barcode skyline, hasPlanningGoal, maintain views and light between buildings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlanningGoal
Context triple: [Barcode skyline, hasPlanningGoal, maintain views and light between buildings]
  • A. hasPrimaryGoal
    Indicates that an entity’s main or most important objective is the specified goal.
  • B. hasPlanningConcept
    Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
  • C. hasPlanningStatus
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • D. hasOperationalGoal
    Indicates that an entity is associated with a specific objective or target it aims to achieve through its operations or activities.
  • E. hasPlanningCharacteristic
    Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
  • F. None of above. chosen

Provenance (4 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_69c008cabc4081909723e2547c9d6cc0 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0639fdad081908492c44d369df8c5 completed March 22, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69c05606fb50819082d1a5a91e5030b6 completed March 22, 2026, 8:50 p.m.
PDg Predicate description generation batch_69c056c965ac8190b938502fa8c74e1b completed March 22, 2026, 8:53 p.m.
Created at: March 22, 2026, 4:25 p.m.