Triple

T32968857
Position Surface form Disambiguated ID Type / Status
Subject Cynwyd neighborhood E843451 entity
Predicate adjacentMunicipalBoundary P33892 FINISHED
Object City of Philadelphia NE NERFINISHED

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: City of Philadelphia | Statement: [Cynwyd neighborhood, adjacentMunicipalBoundary, City of Philadelphia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjacentMunicipalBoundary
Context triple: [Cynwyd neighborhood, adjacentMunicipalBoundary, City of Philadelphia]
  • A. neighbouringMunicipality chosen
    Indicates that one municipality directly borders and is adjacent to another municipality.
  • B. borderingLocalGovernmentArea
    Indicates that one local government area shares a common boundary with another local government area.
  • C. hasMunicipalityBoundaryRole
    Indicates that an entity participates in or is assigned a specific role related to the boundary of a municipality (such as defining, managing, or being affected by that boundary).
  • D. borderingCensusDivision
    Indicates that one census division shares a common boundary with another census division.
  • E. isBorderMunicipality
    Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
  • 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_69f3494b9fc48190bb61c955ba471275 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8cec6d48190bebfa884b2f938c0 completed May 3, 2026, 7:58 p.m.
Created at: May 1, 2026, 1:21 a.m.