Triple

T36630950
Position Surface form Disambiguated ID Type / Status
Subject Bruntsfield Place E904313 entity
Predicate connectsTo P845 FINISHED
Object Leven Street
Leven Street is a street in Edinburgh, Scotland, situated near Bruntsfield and forming part of a key route linking the city’s southside neighborhoods to the city centre.
E2292566 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: Leven Street | Statement: [Bruntsfield Place, connectsTo, Leven Street]
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: Leven Street
Triple: [Bruntsfield Place, connectsTo, Leven Street]
Generated description
Leven Street is a street in Edinburgh, Scotland, situated near Bruntsfield and forming part of a key route linking the city’s southside neighborhoods to the city centre.

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_69f76e6ae750819096911e6e2d4d12c5 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c4b426a88190ab92a82f0e94e925 completed May 3, 2026, 9:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a79acc32194819096664bae90de0828 completed Aug. 10, 2026, 10:49 a.m.
NEDg Description generation batch_6a79ad232ee081909788d1ef86f8462a completed Aug. 10, 2026, 10:51 a.m.
NED2 Entity disambiguation (via description) batch_6a79ad72bef08190843ed5886f2ab085 completed Aug. 10, 2026, 10:52 a.m.
Created at: May 3, 2026, 4:11 p.m.