Triple
T28185561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahlabathini |
E716168
|
entity |
| Predicate | locatedInTraditionalArea |
P88079
|
FINISHED |
| Object | KwaZulu |
—
|
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: KwaZulu | Statement: [Mahlabathini, locatedInTraditionalArea, KwaZulu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTraditionalArea Context triple: [Mahlabathini, locatedInTraditionalArea, KwaZulu]
-
A.
locatedInTraditionalRegion
chosen
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
B.
hasTraditionalArea
Indicates that an entity is associated with or belongs to a customary or historically recognized geographic area.
-
C.
traditionallyResidesIn
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
-
D.
locatedInFormerAdministrativeTerritory
Indicates that an entity is situated within the boundaries of an administrative territory that no longer exists or has been reorganized.
-
E.
locatedInAutonomousRegion
Indicates that one entity is geographically or administratively situated within a self-governing or semi-independent regional territory.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: April 27, 2026, 10:22 p.m.