Triple

T18211360
Position Surface form Disambiguated ID Type / Status
Subject Queen Victoria Square E436038 entity
Predicate hasNearbyStreet P8235 FINISHED
Object Paragon Street
Paragon Street is a central street in Kingston upon Hull, England, known for its proximity to Queen Victoria Square and its mix of shops, services, and pedestrian access.
E1727726 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: Paragon Street | Statement: [Queen Victoria Square, hasNearbyStreet, Paragon 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: Paragon Street
Triple: [Queen Victoria Square, hasNearbyStreet, Paragon Street]
Generated description
Paragon Street is a central street in Kingston upon Hull, England, known for its proximity to Queen Victoria Square and its mix of shops, services, and pedestrian access.

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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e2296f8081908247a6dd08f99b25 completed April 19, 2026, 2:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11bae3c7508190a4d21d3dae476284 completed May 23, 2026, 2:34 p.m.
NEDg Description generation batch_6a11be5eaa64819093fca394daf91d90 completed May 23, 2026, 2:49 p.m.
NED2 Entity disambiguation (via description) batch_6a11bf1dd27c8190b77577de860ac016 completed May 23, 2026, 2:52 p.m.
Created at: April 10, 2026, 10:32 a.m.