Triple

T20303673
Position Surface form Disambiguated ID Type / Status
Subject Rotorua Lakes District E505549 entity
Predicate hasSettlement P1068 FINISHED
Object Reporoa 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: Reporoa | Statement: [Rotorua Lakes District, hasSettlement, Reporoa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reporoa
Context triple: [Rotorua Lakes District, hasSettlement, Reporoa]
  • A. Reporoa chosen
    Reporoa is a rural settlement in New Zealand’s central North Island, situated in the volcanically active Taupō Volcanic Zone and surrounded by geothermal and agricultural landscapes.
  • B. Erakor
    Erakor is a small island and settlement near Efate in Vanuatu, known for its lagoon setting and traditional village life.
  • C. Sukarrieta
    Sukarrieta is a small coastal municipality in the Basque Country in northern Spain, known for its natural surroundings along the Urdaibai Biosphere Reserve.
  • D. Reopalu
    Reopalu is a small settlement located in Järva County in central Estonia.
  • E. Reureu
    Reureu is a village settlement on the island of Aitutaki in the Cook Islands.
  • 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_69e0b4b8ab648190906e18538c250148 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6773e0864819095d272659cd2074d completed April 20, 2026, 6:58 p.m.
Created at: April 16, 2026, 11:17 a.m.