Triple

T16661611
Position Surface form Disambiguated ID Type / Status
Subject Seven Sisters E404872 entity
Predicate locatedOn P40 FINISHED
Object A503 road
The A503 road is a major route in North London connecting areas such as Seven Sisters, Tottenham, and Camden, and providing an important link between inner and outer parts of the city.
E2224841 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: A503 road | Statement: [Seven Sisters, locatedOn, A503 road]
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: A503 road
Triple: [Seven Sisters, locatedOn, A503 road]
Generated description
The A503 road is a major route in North London connecting areas such as Seven Sisters, Tottenham, and Camden, and providing an important link between inner and outer parts of the city.

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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37bfee5448190bb44c4dadba5dcbd completed April 18, 2026, 12:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4076d5c41c8190832bf779bbe06ea0 completed June 28, 2026, 1:20 a.m.
NEDg Description generation batch_6a4077aa5868819088b136de69926f01 completed June 28, 2026, 1:23 a.m.
NED2 Entity disambiguation (via description) batch_6a4078362d0881909b963ee3fe45787e completed June 28, 2026, 1:26 a.m.
Created at: April 10, 2026, 5:18 a.m.