Triple

T21890276
Position Surface form Disambiguated ID Type / Status
Subject Farringdon Road E540521 entity
Predicate hasJunctionWith P1018 FINISHED
Object Rosebery Avenue
Rosebery Avenue is a major street in central London running through Clerkenwell and Islington, known for linking key thoroughfares and serving as a busy route for traffic and buses.
E2262594 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: Rosebery Avenue | Statement: [Farringdon Road, hasJunctionWith, Rosebery Avenue]
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: Rosebery Avenue
Triple: [Farringdon Road, hasJunctionWith, Rosebery Avenue]
Generated description
Rosebery Avenue is a major street in central London running through Clerkenwell and Islington, known for linking key thoroughfares and serving as a busy route for traffic and buses.

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_69e0c47a95908190ae3e19b716accb3d completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f11fc2124c8190a79cf115a1d30283 completed April 28, 2026, 8:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4193a773ec8190a95d8226361c03d7 completed June 28, 2026, 9:35 p.m.
NEDg Description generation batch_6a4194a73dcc8190a4bfba8dd33acd8c completed June 28, 2026, 9:39 p.m.
NED2 Entity disambiguation (via description) batch_6a41956d0f208190be2322f18ed193cf completed June 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 7:06 p.m.