Triple
T24883210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | uMhlathuze Local Municipality |
E622770
|
entity |
| Predicate | industrialPortCity |
P95801
|
FINISHED |
| Object | Richards Bay |
—
|
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: Richards Bay | Statement: [uMhlathuze Local Municipality, industrialPortCity, Richards Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialPortCity Context triple: [uMhlathuze Local Municipality, industrialPortCity, Richards Bay]
-
A.
hasIndustrialPort
chosen
Indicates that a location possesses a port facility specifically equipped and used for industrial or commercial shipping activities.
-
B.
servesIndustrialCity
Indicates that something functions to provide services, support, or utility to an industrial city.
-
C.
isUrbanAndIndustrialHub
Indicates that a place functions as a major center of urban activity and industrial production.
-
D.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
E.
majorPortCity
Indicates that a city functions as a primary maritime port, serving as a major hub for sea transport, trade, or shipping activities.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:25 a.m.