Triple

T7430669
Position Surface form Disambiguated ID Type / Status
Subject Princes Park E171479 entity
Predicate neighbourhoodContext P988 FINISHED
Object adjacent to Princes Park public parklands 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: adjacent to Princes Park public parklands | Statement: [Princes Park, neighbourhoodContext, adjacent to Princes Park public parklands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: neighbourhoodContext
Context triple: [Princes Park, neighbourhoodContext, adjacent to Princes Park public parklands]
  • A. neighborhood chosen
    Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
  • B. hasNeighbourhood
    Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
  • C. neighborhoodCharacteristic
    Indicates that a particular characteristic, feature, or quality is associated with or describes a given neighborhood.
  • D. hasNearbyCommunity
    Indicates that one entity has another community located close to it in geographic or spatial terms.
  • E. formerNeighborhood
    Indicates that an entity was previously located in or associated with a particular neighborhood but is no longer situated there.
  • 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_69c68a63491881909281f73d4d5643bf completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f32324c481908c9ba594e8456728 completed March 27, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69c6f038582c8190bac77c9b5a34b862 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:12 p.m.