Triple

T17472145
Position Surface form Disambiguated ID Type / Status
Subject Port Adelaide-Enfield E425443 entity
Predicate contains P35 FINISHED
Object Hillcrest NE NERFINISHED

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: Hillcrest | Statement: [Port Adelaide-Enfield, contains, Hillcrest]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hillcrest
Context triple: [Port Adelaide-Enfield, contains, Hillcrest]
  • A. Hillcrest chosen
    Hillcrest is a suburban residential area located within the northeastern part of metropolitan Adelaide, South Australia.
  • B. Hillcrest
    Hillcrest is a residential neighborhood in the borough of Queens, New York City, known for its quiet streets, diverse community, and proximity to institutions like Queens College.
  • C. Hillcrest
    Hillcrest is a residential suburb located within Logan City in Queensland, Australia.
  • D. Hillcrest
    Hillcrest is a residential suburb within the coastal city of Burnie in north-west Tasmania, Australia.
  • E. Hillcrest
    Hillcrest is a residential suburb located near Hamilton East in Hamilton, New Zealand, known for its proximity to the University of Waikato and family-friendly amenities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451b8a51081908d94bebe2417e3d3 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.