Triple

T33377217
Position Surface form Disambiguated ID Type / Status
Subject Perinton, New York E854666 entity
Predicate hasPlanningReputation P93104 FINISHED
Object well-developed park and trail network 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: well-developed park and trail network | Statement: [Perinton, New York, hasPlanningReputation, well-developed park and trail network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlanningReputation
Context triple: [Perinton, New York, hasPlanningReputation, well-developed park and trail network]
  • A. haveReputation chosen
    Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
  • B. hasPlanningStatus
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • C. hasPlanningSignificance
    Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
  • D. hasPlanningLevel
    Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
  • E. hasPlanningType
    Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
  • 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_69f3496ca10c8190908640d18fa00832 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd19f791f48190bbb6f6047f9ddc59 completed May 7, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69fd0df365948190bc9bfc7ffd46acd8 completed May 7, 2026, 10:10 p.m.
Created at: May 1, 2026, 1:35 a.m.