Triple
T33495158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondebosch campus |
E857844
|
entity |
| Predicate | transportServedBy |
P1298
|
FINISHED |
| Object |
Jammie Shuttle
Jammie Shuttle is the free bus service that transports students and staff around the University of Cape Town’s campuses and nearby areas.
|
E2052609
|
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: Jammie Shuttle | Statement: [Rondebosch campus, transportServedBy, Jammie Shuttle]
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: Jammie Shuttle Triple: [Rondebosch campus, transportServedBy, Jammie Shuttle]
Generated description
Jammie Shuttle is the free bus service that transports students and staff around the University of Cape Town’s campuses and nearby areas.
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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e56a6a488190aaf731ce3d097505 |
completed | May 3, 2026, 6:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3595bf90fc81908e34a50024ca94ac |
completed | June 19, 2026, 7:17 p.m. |
| NEDg | Description generation | batch_6a3596afcad88190891d62137b93e1bb |
completed | June 19, 2026, 7:21 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a35972e0a908190b5e85121a47577a3 |
completed | June 19, 2026, 7:23 p.m. |
Created at: May 1, 2026, 1:38 a.m.