Triple

T15266017
Position Surface form Disambiguated ID Type / Status
Subject Concord E364902 entity
Predicate hasNeighbouringSuburb P41355 FINISHED
Object Mortlake E309964 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: Mortlake | Statement: [Concord, hasNeighbouringSuburb, Mortlake]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mortlake
Context triple: [Concord, hasNeighbouringSuburb, Mortlake]
  • A. Mortlake chosen
    Mortlake is a riverside suburb in Sydney, Australia, known for its location on the Parramatta River and mix of residential and light industrial areas.
  • B. Mortlake
    Mortlake is a riverside district in southwest London on the River Thames, known as the traditional finishing point of the annual Oxford–Cambridge Boat Race.
  • C. Ingliston
    Ingliston is a village and district in western Edinburgh, Scotland, best known for hosting the Royal Highland Centre and being adjacent to Edinburgh Airport.
  • D. Burwood
    Burwood is a suburb in Sydney’s Inner West known for its diverse community, busy commercial centre, and strong transport links to the city.
  • E. Oakleigh
    Oakleigh is a residential and commercial suburb in Melbourne’s south-east, known for its strong Greek community, vibrant shopping precincts, and proximity to major transport links.
  • 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_69d85a0f08408190b3c3259ae35d79d2 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00851c5b88190a296b6a105d3ee30 completed April 15, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef6fc290819096ef03f8ecae8876 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:14 a.m.