Triple
T31837956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German South-West Africa |
E812723
|
entity |
| Predicate | postWarAdministrator |
P6698
|
FINISHED |
| Object | Union of South Africa |
—
|
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: Union of South Africa | Statement: [German South-West Africa, postWarAdministrator, Union of South Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWarAdministrator Context triple: [German South-West Africa, postWarAdministrator, Union of South Africa]
-
A.
postWarPosition
Indicates the role, status, or position an entity held in the period following a war.
-
B.
postWarOrder
Indicates the arrangement of political, economic, and social relations established among actors after a war has ended.
-
C.
postWarOccupation
chosen
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
D.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
-
E.
operatorAfterWar
Indicates that one entity serves or functions as an operator after the occurrence or end of a war.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aff437b0819084d87a8f59be5202 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:48 p.m.