Triple

T25566140
Position Surface form Disambiguated ID Type / Status
Subject Liverpool Street to Enfield Town line E640840 entity
Predicate connectsStation P845 FINISHED
Object Wood Street
Wood Street is a suburban railway station in northeast London served by London Overground services on the route between central London and Enfield.
E1818522 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: Wood Street | Statement: [Liverpool Street to Enfield Town line, connectsStation, Wood Street]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Wood Street
Triple: [Liverpool Street to Enfield Town line, connectsStation, Wood Street]
Generated description
Wood Street is a suburban railway station in northeast London served by London Overground services on the route between central London and Enfield.

Provenance (5 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_69e75dc1beb08190bac7d76b8d6e7bc4 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8fc5dc481908dbb660bcde9cb4e completed May 2, 2026, 1:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4329e605088190b23701fd67b034bf completed June 30, 2026, 2:28 a.m.
NEDg Description generation batch_6a4331fe687881908e2a6dfa0da7e5d7 completed June 30, 2026, 3:03 a.m.
NED2 Entity disambiguation (via description) batch_6a433279afb481909a95a1a57c283bea completed June 30, 2026, 3:05 a.m.
Created at: April 21, 2026, 3:49 p.m.