Triple

T12748994
Position Surface form Disambiguated ID Type / Status
Subject Thandwe E304681 entity
Predicate historicalName P65 FINISHED
Object Sandoway E999408 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: Sandoway | Statement: [Thandwe, historicalName, Sandoway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sandoway
Context triple: [Thandwe, historicalName, Sandoway]
  • A. Sandoway chosen
    Sandoway is the former English name for Thandwe, a coastal town in Rakhine State, western Myanmar, known historically as an important seaport.
  • B. Stonehaven
    Stonehaven is a coastal town in Aberdeenshire, Scotland, known for its picturesque harbor, historic Dunnottar Castle nearby, and role as a gateway between the Highlands and Lowlands.
  • C. Leamouth
    Leamouth is a riverside district in East London where the River Lea meets the River Thames, known for its former industrial docks and recent waterside redevelopment.
  • D. Southwood
    Southwood is a suburban residential area within the Borough of Rushmoor in Hampshire, England.
  • E. Bynea
    Bynea is a village in Carmarthenshire, Wales, situated near the Loughor estuary and forming part of the Llanelli urban 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd75f508190aaae0969f33d1523 completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f684ee2ab4819099194d115d2e5a15 completed May 2, 2026, 11:12 p.m.
Created at: April 9, 2026, 5:27 p.m.