Triple

T25273158
Position Surface form Disambiguated ID Type / Status
Subject Johannesburg public transport network E633620 entity
Predicate dominantParatransitMode P28705 FINISHED
Object minibus taxi 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: minibus taxi | Statement: [Johannesburg public transport network, dominantParatransitMode, minibus taxi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dominantParatransitMode
Context triple: [Johannesburg public transport network, dominantParatransitMode, minibus taxi]
  • A. paratransitSystemName
    Indicates the name assigned to a specific paratransit transportation system or service.
  • B. publicTransitMode chosen
    Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
  • C. hasPublicTransitMode
    Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
  • D. transportModeImportant
    Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
  • E. hasPublicTransitRole
    Indicates that an entity holds a specific functional role or responsibility within a public transit system.
  • 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_69e75a92f48881909974ff9c11150a2e completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6456608190b94e7c2e2c2a4824 completed May 2, 2026, 6:03 p.m.
Created at: April 21, 2026, 1:17 p.m.