Triple
T34201062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebank Gautrain station |
E877384
|
entity |
| Predicate | ticketingHallLocation |
P43373
|
FINISHED |
| Object | underground concourse |
—
|
LITERAL 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: underground concourse | Statement: [Rosebank Gautrain station, ticketingHallLocation, underground concourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketingHallLocation Context triple: [Rosebank Gautrain station, ticketingHallLocation, underground concourse]
-
A.
ticketingLocation
chosen
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
-
B.
concertHallLocation
Indicates the place where a concert hall is situated or located.
-
C.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
-
D.
eventLocationDetail
Indicates the specific place or venue where an event occurs, often providing more granular location information than a general address or area.
-
E.
ticketingContext
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
- F. None of above.
Provenance (3 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7104a65688190955e27ad495a49dc |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.