Triple

T16247905
Position Surface form Disambiguated ID Type / Status
Subject Bel Air–Beverly Crest Community Plan Area E394421 entity
Predicate hasInfrastructureConcern P122338 FINISHED
Object limited roadway access 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: limited roadway access | Statement: [Bel Air–Beverly Crest Community Plan Area, hasInfrastructureConcern, limited roadway access]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInfrastructureConcern
Context triple: [Bel Air–Beverly Crest Community Plan Area, hasInfrastructureConcern, limited roadway access]
  • A. hasInfrastructureAbove
    Indicates that one entity’s infrastructure is physically located above or over another entity.
  • B. hasManagementConcern
    Indicates that one entity has responsibility, authority, or involvement in overseeing, directing, or managing another entity or activity.
  • C. hasInfrastructureType
    Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
  • D. infrastructureNeed
    Indicates that an entity requires the development, improvement, or provision of infrastructure to meet its functional or operational needs.
  • E. hasSecurityInfrastructure
    Indicates that one entity possesses, implements, or is equipped with security-related systems, measures, or infrastructure in relation to another entity or context.
  • 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_69d87f2171208190951025e526947816 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e245942460819080897afad0d2fe09 completed April 17, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69e219ee6f6481909663b388dc99770a completed April 17, 2026, 11:30 a.m.
PDg Predicate description generation batch_69e21e55a2388190b29a045a8c608ba4 completed April 17, 2026, 11:49 a.m.
Created at: April 10, 2026, 5:04 a.m.