Triple
T8166946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natal, South Africa |
E190715
|
entity |
| Predicate | joinedUnionOfSouthAfrica |
P15931
|
FINISHED |
| Object | 1910 |
—
|
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: 1910 | Statement: [Natal, South Africa, joinedUnionOfSouthAfrica, 1910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedUnionOfSouthAfrica Context triple: [Natal, South Africa, joinedUnionOfSouthAfrica, 1910]
-
A.
SouthernAfricanDevelopmentCommunityMember
Indicates that an entity is a member state or participant in the Southern African Development Community (SADC).
-
B.
joinedEastAfricanCommunity
Indicates that an entity became a member state of the East African Community (EAC).
-
C.
admittedToUnionFrom
Indicates that an entity (such as a state or region) was admitted into a union or larger political entity from a specified prior jurisdiction or status.
-
D.
enteredConfederation
chosen
Indicates that an entity became a member of, or formally joined, a confederation.
-
E.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb46680fac81908df134df9bf84915 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.