Triple

T19230601
Position Surface form Disambiguated ID Type / Status
Subject Mile End E480860 entity
Predicate hasStreetLifeCharacteristic P135267 FINISHED
Object pedestrian-friendly 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: pedestrian-friendly | Statement: [Mile End, hasStreetLifeCharacteristic, pedestrian-friendly]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStreetLifeCharacteristic
Context triple: [Mile End, hasStreetLifeCharacteristic, pedestrian-friendly]
  • A. hasDowntownCharacteristic
    Indicates that something possesses a feature, quality, or attribute typically associated with a downtown area.
  • B. hasNightlifeArea
    Indicates that a place contains or is associated with an area characterized by nightlife activities such as bars, clubs, or evening entertainment venues.
  • C. isUrbanStreet
    Indicates that a given street is located within an urban area or city environment rather than a rural or suburban setting.
  • D. hasStreet
    Indicates that an entity is located on, associated with, or identified by a particular street.
  • E. hasUrbanFeature
    Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
  • 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_69d8e8ccb8f48190ad420098e74fb1db completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fa9ce5e081909df994841ce476d5 completed April 20, 2026, 10:06 a.m.
PD Predicate disambiguation batch_69e4dcfae6f081909cc173cf71a5005c completed April 19, 2026, 1:47 p.m.
PDg Predicate description generation batch_69e4debc39ac81908b7c5ef797046360 completed April 19, 2026, 1:55 p.m.
Created at: April 10, 2026, 1:25 p.m.