Triple

T18604357
Position Surface form Disambiguated ID Type / Status
Subject Alonnah E454699 entity
Predicate hasNearbyLocality P3883 FINISHED
Object Lunawanna 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: Lunawanna | Statement: [Alonnah, hasNearbyLocality, Lunawanna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lunawanna
Context triple: [Alonnah, hasNearbyLocality, Lunawanna]
  • A. Lunawanna chosen
    Lunawanna is a small coastal settlement on Bruny Island in Tasmania, Australia, known for its tranquil bays and natural scenery.
  • B. Loelva
    Loelva is a river flowing through Norway’s scenic Loen valley, known for its glacial origins and striking turquoise waters.
  • C. Wandella
    Wandella is a rural locality within New South Wales, Australia, administered as part of the Carrathool Shire local government area.
  • D. Mernere
    Mernere is the Egyptian name of Pharaoh Merenre Nemtyemsaf I, a 6th Dynasty ruler of the Old Kingdom.
  • E. Lilliwaup
    Lilliwaup is a small unincorporated community in Mason County, Washington, known for its scenic location along Hood Canal and access to shellfishing and outdoor recreation.
  • 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e547535b8c8190ab5a8a92f15f2bcb completed April 19, 2026, 9:21 p.m.
Created at: April 10, 2026, 11:45 a.m.