Triple

T12304308
Position Surface form Disambiguated ID Type / Status
Subject Currie E293313 entity
Predicate hasPostTown P2711 FINISHED
Object Currie E293313 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: Currie | Statement: [Currie, hasPostTown, Currie]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Currie
Context triple: [Currie, hasPostTown, Currie]
  • A. Currie
    Currie is a Scottish-origin surname borne by various notable individuals across fields such as military, politics, and the arts.
  • B. Currie chosen
    Currie is a suburban village on the outskirts of Edinburgh, Scotland, known for its historic character and location along the Water of Leith.
  • C. Currie
    Currie is the principal township and administrative center of King Island in the Bass Strait, Tasmania, Australia.
  • D. Raikes Currie
    Raikes Currie was a 19th-century British banker and Whig politician known for his involvement in finance and public life.
  • E. Seddon
    Seddon is a small rural town in New Zealand’s Marlborough region, known for its surrounding vineyards and proximity to the Awatere Valley wine-growing area.
  • 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_69d6ab6a2b50819082f6aedd32ed608a completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93edca2648190987eef19599e340c completed April 10, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69f61e7f8fd08190bdef3bb761d53f97 completed May 2, 2026, 3:55 p.m.
Created at: April 8, 2026, 9:53 p.m.