Triple

T6320493
Position Surface form Disambiguated ID Type / Status
Subject Otago E141724 entity
Predicate hasTown P847 FINISHED
Object Roxburgh E565148 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: Roxburgh | Statement: [Otago, hasTown, Roxburgh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roxburgh
Context triple: [Otago, hasTown, Roxburgh]
  • A. Roxburgh
    Roxburgh is a historic area in the Scottish Borders that was once a significant medieval royal burgh and fortress.
  • B. Roxburgh chosen
    Roxburgh is a small town in Central Otago, New Zealand, known for its fruit orchards, hydroelectric dam, and scenic setting in the Clutha River valley.
  • C. Sholto
    Sholto is a masculine given name of Scottish origin, historically associated with figures such as military leaders and nobles.
  • D. Kincorth
    Kincorth is a residential area in the south of Aberdeen, Scotland, known for its post-war housing and proximity to the River Dee.
  • E. Courtfield
    Courtfield is a residential district within the Royal Borough of Kensington and Chelsea in west London, known for its affluent character and proximity to central London amenities.
  • 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_69c008d13b8c8190be47d896eb735605 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c064c61f008190b316b9ff1023b057 completed March 22, 2026, 9:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69c5e48485308190adc2208ad46faaa7 completed March 27, 2026, 1:59 a.m.
Created at: March 22, 2026, 4:29 p.m.