Triple

T19007720
Position Surface form Disambiguated ID Type / Status
Subject Rainworth E465132 entity
Predicate civilParish P2739 FINISHED
Object Rainworth 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: Rainworth | Statement: [Rainworth, civilParish, Rainworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rainworth
Context triple: [Rainworth, civilParish, Rainworth]
  • A. Rainworth chosen
    Rainworth is a village in Nottinghamshire, England, known as a residential community near the town of Mansfield.
  • B. Northdown
    Northdown is a small rural locality in northern Tasmania, Australia, situated within the Latrobe Council region.
  • C. Gortnahoe
    Gortnahoe is a small rural village in Ireland known for its agricultural surroundings and traditional community life.
  • D. Flamborough
    Flamborough is a largely rural community within the city of Hamilton, Ontario, known for its small towns, conservation areas, and agricultural landscape.
  • E. Loughbrickland
    Loughbrickland is a small village in County Down, Northern Ireland, known for its historic coaching inn heritage and proximity to the A1 road between Belfast and Dublin.
  • 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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6a623c481908d22c9bfad9e2939 completed April 20, 2026, 7:32 a.m.
Created at: April 10, 2026, 12:01 p.m.