Triple

T1999373
Position Surface form Disambiguated ID Type / Status
Subject Parbold railway station E43429 entity
Predicate locatedIn P40 FINISHED
Object Parbold E43429 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: Parbold | Statement: [Parbold railway station, locatedIn, Parbold]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parbold
Context triple: [Parbold railway station, locatedIn, Parbold]
  • A. Parbold chosen
    Parbold is a village in Lancashire, England, known for its scenic setting near the River Douglas and the Leeds and Liverpool Canal.
  • B. Balfe
    Balfe is a surname of Irish origin borne by various notable individuals in fields such as music, acting, and politics.
  • C. Colsterworth
    Colsterworth is a village in Lincolnshire, England, best known for its proximity to Woolsthorpe Manor, the birthplace of Sir Isaac Newton.
  • D. Bayertor
    Bayertor is a well-preserved medieval city gate in Landsberg am Lech, Germany, renowned as one of the town’s most prominent historical landmarks.
  • E. Sandiacre
    Sandiacre is a village and civil parish in the Erewash district of Derbyshire, England, situated near the border with Nottinghamshire.
  • 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_69a88715dbbc8190b2299e29e955d997 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb87dc8d08190907a6579c2b26d01 completed March 7, 2026, 5:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae034122ec819096a72685b34c84b9 completed March 8, 2026, 11:16 p.m.
Created at: March 4, 2026, 7:37 p.m.