Triple

T19028804
Position Surface form Disambiguated ID Type / Status
Subject St John’s Gate E465679 entity
Predicate streetAddress P606 FINISHED
Object St John’s Lane
St John’s Lane is a historic street in the Clerkenwell area of London, known for its medieval and early modern architecture and its association with the Order of St John.
E1982394 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: St John’s Lane | Statement: [St John’s Gate, streetAddress, St John’s Lane]
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: St John’s Lane
Triple: [St John’s Gate, streetAddress, St John’s Lane]
Generated description
St John’s Lane is a historic street in the Clerkenwell area of London, known for its medieval and early modern architecture and its association with the Order of St John.

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_69d8dd0359648190bc2a9202c5cf29d2 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d73ec9088190a98e214bd56e8622 completed April 20, 2026, 7:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e7fb2a27081909d14476e87263821 completed June 14, 2026, 10:17 a.m.
NEDg Description generation batch_6a2e80bfc09c81908b0f21d5dc3629e9 completed June 14, 2026, 10:21 a.m.
NED2 Entity disambiguation (via description) batch_6a2e81c63b8081909989e5e18ce19954 completed June 14, 2026, 10:26 a.m.
Created at: April 10, 2026, 12:02 p.m.