Triple

T36238875
Position Surface form Disambiguated ID Type / Status
Subject Umbilo River E891455 entity
Predicate passesNear P416 FINISHED
Object Umbilo suburb
Umbilo suburb is a residential area in Durban, South Africa, known for its mixed housing, light industry, and proximity to key transport routes and educational institutions.
E2175033 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: Umbilo suburb | Statement: [Umbilo River, passesNear, Umbilo suburb]
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: Umbilo suburb
Triple: [Umbilo River, passesNear, Umbilo suburb]
Generated description
Umbilo suburb is a residential area in Durban, South Africa, known for its mixed housing, light industry, and proximity to key transport routes and educational institutions.

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_69f76e44993481908fa75e4c48d0aab3 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5cddac081909ca5deb9e5a30331 completed May 3, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a394d4031e481909e6ec474a8d28cd2 completed June 22, 2026, 2:57 p.m.
NEDg Description generation batch_6a394ea065408190ace4876aaadf8f58 completed June 22, 2026, 3:02 p.m.
NED2 Entity disambiguation (via description) batch_6a39513b450c8190b6aef8271cd1d481 completed June 22, 2026, 3:14 p.m.
Created at: May 3, 2026, 4:09 p.m.