Triple

T7027718
Position Surface form Disambiguated ID Type / Status
Subject Deva E163189 entity
Predicate hasStreetPlanInfluenceOn P19359 FINISHED
Object street layout of Chester 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: street layout of Chester | Statement: [Deva, hasStreetPlanInfluenceOn, street layout of Chester]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStreetPlanInfluenceOn
Context triple: [Deva, hasStreetPlanInfluenceOn, street layout of Chester]
  • A. hasStreetPlan
    Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
  • B. streetPlanBy
    Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
  • C. urbanPlanningFunction
    Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
  • D. urbanPlanInspiredBy chosen
    Indicates that an urban planning design, strategy, or project is conceptually derived from, modeled on, or significantly influenced by another plan, precedent, or source.
  • E. hasStreetLayoutCenteredOn
    Indicates that the spatial organization or pattern of streets in one place is arranged with a particular feature or location as its central focus or reference point.
  • 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_69c6885d691c81908cf7d31083113886 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e458ad9c81908c3f492b317ce291 completed March 27, 2026, 8:11 p.m.
PD Predicate disambiguation batch_69c6e1b9a2488190aea351d96afa5a12 completed March 27, 2026, 7:59 p.m.
Created at: March 27, 2026, 2:35 p.m.