Triple

T14062820
Position Surface form Disambiguated ID Type / Status
Subject City of Gardens E338388 entity
Predicate associatedCityFeature P1495 FINISHED
Object public parks 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: public parks | Statement: [City of Gardens, associatedCityFeature, public parks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedCityFeature
Context triple: [City of Gardens, associatedCityFeature, public parks]
  • A. hostCityFeature
    Indicates that a particular feature, attribute, or characteristic is associated with or present in a host city.
  • B. cityAssociatedWith
    Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
  • C. hasUrbanFeature chosen
    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.
  • D. iconicFeature
    Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
  • E. linkedCity
    Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de568876308190840361dcaf10bd45 completed April 14, 2026, 3 p.m.
PD Predicate disambiguation batch_69de05adef888190b023ab42ef5076b6 completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:21 p.m.