Triple

T26366465
Position Surface form Disambiguated ID Type / Status
Subject Northumberland Park E660346 entity
Predicate hasLocalAuthorityWard P61409 FINISHED
Object Northumberland Park ward
Northumberland Park ward is an electoral division within the London Borough of Haringey, used for local government representation and administration.
E1723140 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: Northumberland Park ward | Statement: [Northumberland Park, hasLocalAuthorityWard, Northumberland Park ward]
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: Northumberland Park ward
Triple: [Northumberland Park, hasLocalAuthorityWard, Northumberland Park ward]
Generated description
Northumberland Park ward is an electoral division within the London Borough of Haringey, used for local government representation and administration.

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_69ee8126d52c8190bc0b34337c2c9aa8 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f6102c248c8190886da68d61d006dc completed May 2, 2026, 2:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a119a6fa688819083622cfadea38010 completed May 23, 2026, 12:15 p.m.
NEDg Description generation batch_6a119c705b70819080eb0eb7ffa2492f completed May 23, 2026, 12:24 p.m.
NED2 Entity disambiguation (via description) batch_6a119d7e21e08190a86e84784dfa9b03 completed May 23, 2026, 12:28 p.m.
Created at: April 26, 2026, 10:55 p.m.