Triple
T37013662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandton Gautrain station |
E916016
|
entity |
| Predicate | openedForAirportService |
P180144
|
FINISHED |
| Object | 2010-06-08 |
—
|
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: 2010-06-08 | Statement: [Sandton Gautrain station, openedForAirportService, 2010-06-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForAirportService Context triple: [Sandton Gautrain station, openedForAirportService, 2010-06-08]
-
A.
openedForAirportAccess
chosen
Indicates that something has been made accessible or put into operation specifically to allow access to an airport.
-
B.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
C.
openedForServiceTo
Indicates that one entity has been made available or activated to provide service or functionality to another entity.
-
D.
openedAirportBranch
Indicates that an entity established and began operating a branch or location at an airport.
-
E.
openedAsPartOfAirport
Indicates that something was opened concurrently with, or as an integral component of, the opening of an airport.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:14 p.m.