Triple

T8209230
Position Surface form Disambiguated ID Type / Status
Subject Culross Abbey E191770 entity
Predicate locatedIn P40 FINISHED
Object Culross E36479 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: Culross | Statement: [Culross Abbey, locatedIn, Culross]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Culross
Context triple: [Culross Abbey, locatedIn, Culross]
  • A. Culross chosen
    Culross is a historic coastal village in Fife, Scotland, known for its well-preserved 16th–17th century buildings and picturesque harbour.
  • B. Kelso
    Kelso is a historic market town in the Scottish Borders, known for its picturesque setting at the confluence of the Rivers Tweed and Teviot and the ruins of Kelso Abbey.
  • C. Willits
    Willits is a small city in Northern California known as the "Gateway to the Redwoods" and for its historic Skunk Train.
  • 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. Parkeston
    Parkeston is a village and port area in Essex, England, situated near Harwich and known historically for its railway and maritime connections.
  • 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_69ca82c7f3e08190857bf1fc63b2a10c completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb76dc784881908e1f63ac907cdd01 completed March 31, 2026, 7:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69ccedda69148190b8c221221de5dae5 completed April 1, 2026, 10:05 a.m.
Created at: March 30, 2026, 5:44 p.m.