Triple

T37212322
Position Surface form Disambiguated ID Type / Status
Subject Grand Reims E922639 entity
Predicate hasUrbanPlanningCompetence P61342 FINISHED
Object local urban plans 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: local urban plans | Statement: [Grand Reims, hasUrbanPlanningCompetence, local urban plans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUrbanPlanningCompetence
Context triple: [Grand Reims, hasUrbanPlanningCompetence, local urban plans]
  • A. hasUrbanPlanning chosen
    Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
  • B. hasUrbanPlanner
    Indicates that an entity is associated with or utilizes a specific urban planner responsible for planning or managing its urban development.
  • C. hasUrbanDesign
    Indicates that an entity possesses or is associated with a specific urban design plan, feature, or configuration.
  • D. hasUrbanPlanningRule
    Indicates that an entity is subject to, governed by, or associated with a specific urban planning rule or regulation.
  • E. hasCityPlanningContext
    Indicates that something is associated with, relevant to, or situated within a particular city planning context, such as urban development, zoning, or land-use planning.
  • 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_69f76ea6f5288190b8d9988f613811c0 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb78cbef988190b8f79d946b46e6b2 completed May 6, 2026, 5:22 p.m.
PD Predicate disambiguation batch_69fb5a9ac5a08190b24ef308963fc52b completed May 6, 2026, 3:13 p.m.
Created at: May 3, 2026, 4:15 p.m.