Triple

T6862192
Position Surface form Disambiguated ID Type / Status
Subject Royal Melbourne Hospital E158308 entity
Predicate locatedIn P40 FINISHED
Object Parkville, Victoria E624369 NE 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: Parkville, Victoria | Statement: [Royal Melbourne Hospital, locatedIn, Parkville, Victoria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parkville, Victoria
Context triple: [Royal Melbourne Hospital, locatedIn, Parkville, Victoria]
  • A. Parkville, Victoria chosen
    Parkville, Victoria is an inner-city suburb of Melbourne known for its major universities, medical and research institutions, and expansive parklands including Royal Park.
  • B. Pakenham
    Pakenham is a rural village and civil parish in Suffolk, England, known for its historic watermill and windmill.
  • C. Kilmore
    Kilmore is a small settlement located in the Sleat peninsula area on the Isle of Skye in Scotland.
  • D. Burwood, Victoria
    Burwood, Victoria is a suburban area of Melbourne, Australia, known for its residential character and as a key educational hub anchored by Deakin University.
  • E. Tullamarine, Victoria
    Tullamarine, Victoria is a suburb in Melbourne best known as the location of the city’s primary international airport.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68830cdbc8190a8301c7a9d9f651a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d887d6648190a0c2d1cb1b284bfe completed March 27, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7511828608190b3a206629b27d410 completed March 28, 2026, 3:55 a.m.
Created at: March 27, 2026, 2:21 p.m.