Triple
T37815321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PWV conurbation |
E942757
|
entity |
| Predicate | includesCityRegion |
P174333
|
FINISHED |
| Object | Pretoria |
E5262
|
NE 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: Pretoria | Statement: [PWV conurbation, includesCityRegion, Pretoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCityRegion Context triple: [PWV conurbation, includesCityRegion, Pretoria]
-
A.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
B.
linkedCityRegion
chosen
Indicates that a city is associated with, belongs to, or is administratively connected to a specific region.
-
C.
capitalRegionIncluded
Indicates that a specified region contains or encompasses the capital area of a given political or administrative entity.
-
D.
terminalCityRegion
Indicates that a city serves as the terminal (end-point) location within a specified region for a route, line, or connection.
-
E.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
- F. None of above.
Provenance (4 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412c9b62bc8190a53d5b2b28efdf2b |
completed | June 28, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.