Triple

T16065392
Position Surface form Disambiguated ID Type / Status
Subject Wivenhoe Dam E389718 entity
Predicate locatedNear P294 FINISHED
Object Fernvale E1109415 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: Fernvale | Statement: [Wivenhoe Dam, locatedNear, Fernvale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fernvale
Context triple: [Wivenhoe Dam, locatedNear, Fernvale]
  • A. Fernvale chosen
    Fernvale is a small rural town in Queensland, Australia, known for its country atmosphere and proximity to the Brisbane River and Wivenhoe Dam.
  • B. Birch Vale
    Birch Vale is a small village in the High Peak district of Derbyshire, England, situated in the Peak District near New Mills.
  • C. Hurlyvale
    Hurlyvale is a residential suburb located within the greater Bedfordview area in Gauteng, South Africa.
  • D. Lantzville
    Lantzville is a small coastal community and district municipality on central Vancouver Island in British Columbia, Canada, known for its residential character and seaside setting.
  • E. Birchgrove
    Birchgrove is a harbourside inner-west suburb of Sydney, Australia, known for its waterfront views, historic homes, and proximity to the city centre.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1837bec688190a77ad347600b6bdc completed April 17, 2026, 12:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe47ef6648190bf1fe216e78ef660 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:57 a.m.