Triple

T8003553
Position Surface form Disambiguated ID Type / Status
Subject Bishop of Repton E186309 entity
Predicate namedAfter P63 FINISHED
Object Repton E156363 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: Repton | Statement: [Bishop of Repton, namedAfter, Repton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Repton
Context triple: [Bishop of Repton, namedAfter, Repton]
  • A. Repton chosen
    Repton is a historic English village in Derbyshire best known for its ancient abbey and prestigious Repton School.
  • B. Rustington
    Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
  • C. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • D. Poynton
    Poynton is a town in Cheshire, England, known for its former coal mining industry and distinctive shared-space central junction.
  • E. Nether Wallop
    Nether Wallop is a small historic village in Hampshire, England, known for its picturesque rural character and traditional thatched cottages.
  • 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_69ca82aaaf24819084b94d18f699ba53 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3cf443e48190ac9e83343ff4019e completed March 31, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc5697ac9081909fe7ca06d0c3ef38 completed March 31, 2026, 11:19 p.m.
Created at: March 30, 2026, 5:18 p.m.