Triple

T20141989
Position Surface form Disambiguated ID Type / Status
Subject Bethany Village E491191 entity
Predicate hasUrbanPlanningModel P72019 FINISHED
Object master-planned community neighborhood 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: master-planned community neighborhood | Statement: [Bethany Village, hasUrbanPlanningModel, master-planned community neighborhood]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUrbanPlanningModel
Context triple: [Bethany Village, hasUrbanPlanningModel, master-planned community neighborhood]
  • A. hasUrbanPlanning
    Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
  • B. hasUrbanModel chosen
    Indicates that an entity is associated with or characterized by a specific urban planning or city-scale representation model.
  • C. hasUrbanPlanner
    Indicates that an entity is associated with or utilizes a specific urban planner responsible for planning or managing its urban development.
  • D. hasUrbanPlanningRule
    Indicates that an entity is subject to, governed by, or associated with a specific urban planning rule or regulation.
  • E. hasUrbanDesign
    Indicates that an entity possesses or is associated with a specific urban design plan, feature, or configuration.
  • 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_69da6265f8f0819080b29c752a574088 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e6679bcf2c8190ac6e969178d8acde completed April 20, 2026, 5:51 p.m.
PD Predicate disambiguation batch_69e54cfb0d0081908e789b9b57e96668 completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 11:33 p.m.