Triple
T8957016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Street (Pretoria) |
E213497
|
entity |
| Predicate | isCentralBusinessDistrictAxis |
P38662
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Church Street (Pretoria), isCentralBusinessDistrictAxis, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralBusinessDistrictAxis Context triple: [Church Street (Pretoria), isCentralBusinessDistrictAxis, true]
-
A.
isDowntownAxis
chosen
Indicates that something serves as or lies along the main central axis of a downtown area.
-
B.
isDowntownCoreOf
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
C.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
-
D.
isDowntownHub
Indicates that a location functions as a central, primary hub within a city’s downtown area.
-
E.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6728965881908e9f14aaee0c5a18 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.