Triple

T28304557
Position Surface form Disambiguated ID Type / Status
Subject SE19 E713803 entity
Predicate locatedIn P40 FINISHED
Object London SE postcode area
The London SE postcode area is a group of southeast London postal districts covering parts of boroughs such as Southwark, Lewisham, Greenwich, and others.
 E1810838 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: London SE postcode area | Statement: [SE19, locatedIn, London SE postcode area]
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: London SE postcode area
Triple: [SE19, locatedIn, London SE postcode area]
Generated description
The London SE postcode area is a group of southeast London postal districts covering parts of boroughs such as Southwark, Lewisham, Greenwich, and others.

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_69efb524ab688190a1ce7ee7c9520932 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f644b5d814819098c20ea8f6051ce8 completed May 2, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a160736cf4c81909bf19d282de2194b completed May 26, 2026, 8:48 p.m.
NEDg Description generation batch_6a1612bdafc081908b0cd7cb342156f7 completed May 26, 2026, 9:38 p.m.
NED2 Entity disambiguation (via description) batch_6a161367f06c8190b6c19f1f3f728f00 completed May 26, 2026, 9:40 p.m.
Created at: April 27, 2026, 11:37 p.m.