Triple

T25273154
Position Surface form Disambiguated ID Type / Status
Subject Johannesburg public transport network E633620 entity
Predicate primaryBRTSystem P37810 FINISHED
Object Rea Vaya NE NERFINISHED

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: Rea Vaya | Statement: [Johannesburg public transport network, primaryBRTSystem, Rea Vaya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryBRTSystem
Context triple: [Johannesburg public transport network, primaryBRTSystem, Rea Vaya]
  • A. rapidTransitSystem
    Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
  • B. primaryBus
    Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
  • C. hasBRTLine chosen
    Indicates that a bus rapid transit (BRT) line is present, operates on, or serves the referenced entity.
  • D. primaryTramSystem
    Indicates that a tram system serves as the main or most important tram network associated with a given place or organization.
  • E. hasBusRapidTransitFeatures
    Indicates that a transportation route or corridor includes design or operational elements characteristic of bus rapid transit systems.
  • 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_69f7431c0eec81909ead443e07d75e18 completed May 3, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69f74143cf708190a12d487884298437 completed May 3, 2026, 12:36 p.m.
Created at: April 21, 2026, 1:17 p.m.