Triple

T7890532
Position Surface form Disambiguated ID Type / Status
Subject M6 E183218 entity
Predicate passesNear P416 FINISHED
Object Preston E24766 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: Preston | Statement: [M6, passesNear, Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Preston
Context triple: [M6, passesNear, Preston]
  • A. Preston chosen
    Preston is a historic industrial city in Lancashire, England, known for its role in the Industrial Revolution and its status as a major urban center in the North West.
  • B. Preston
    Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
  • C. Preston
    Preston is a masculine given name of English origin that has been used both as a first name and a surname.
  • D. Preston
    Preston is a suburb in Melbourne, Australia, served by its own railway station on the metropolitan train network.
  • E. Preston
    Preston is a residential area and suburb within the Metropolitan Borough of North Tyneside in North East England.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39ee137081908e87e35016c3a176 completed March 31, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbdecc6c5c8190af4445928ce1132f completed March 31, 2026, 2:48 p.m.
Created at: March 30, 2026, 5 p.m.