Triple

T5528545
Position Surface form Disambiguated ID Type / Status
Subject EFL E144987 entity
Predicate headquartersLocation P62 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: [EFL, headquartersLocation, Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Preston
Context triple: [EFL, headquartersLocation, 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. Prenton
    Prenton is a suburban residential area on the Wirral Peninsula in Merseyside, England, known for its parks, schools, and proximity to Birkenhead.
  • E. Manchester–Preston
    Manchester–Preston is a key railway corridor in North West England linking the city of Manchester with Preston and serving as part of the region’s intercity and commuter network.
  • 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_69c008f9955881909bfa8348b56b4739 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f8b6c348190b7d414dc1907d09a completed March 22, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c02801cbf881909da344a057520f32 completed March 22, 2026, 5:33 p.m.
Created at: March 22, 2026, 3:34 p.m.