Triple

T25783790
Position Surface form Disambiguated ID Type / Status
Subject Toorak railway station E649361 entity
Predicate servesAreaCharacteristic P3938 FINISHED
Object affluent residential area 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: affluent residential area | Statement: [Toorak railway station, servesAreaCharacteristic, affluent residential area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesAreaCharacteristic
Context triple: [Toorak railway station, servesAreaCharacteristic, affluent residential area]
  • A. serviceAreaCharacteristic chosen
    Indicates a relationship where a service area is associated with a specific attribute or feature that characterizes it.
  • B. coreAreaCharacteristic
    Indicates that a characteristic or feature is specifically associated with the core area of something, rather than its peripheral or secondary parts.
  • C. characteristicOfZone
    Indicates that a particular characteristic, feature, or property is associated with and defines a specific zone or area.
  • D. areaServedType
    Indicates the type or category of area that is served by an entity or service.
  • E. hasCatchmentAreaCharacteristic
    Indicates that a catchment area possesses a specified characteristic, feature, or property.
  • 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_69e7ab33e9308190afe415dc6f9e8876 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6df450014819099d118e5c2d697fa completed May 3, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69f6de07836481908785cde9c511920b completed May 3, 2026, 5:32 a.m.
Created at: April 22, 2026, 5:52 a.m.