Triple
T31837966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German South-West Africa |
E812723
|
entity |
| Predicate | languageOfColonialPower |
P181391
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [German South-West Africa, languageOfColonialPower, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfColonialPower Context triple: [German South-West Africa, languageOfColonialPower, German]
-
A.
languageOfColonialSettlers
Indicates the language historically spoken by colonial settlers in a given place or context.
-
B.
hasColonialLanguage
Indicates that one entity uses or is associated with the colonial language historically imposed or introduced by another entity.
-
C.
officialLanguageDuringColonialPeriod
Indicates that a language served as the official language of administration or governance in a territory during its colonial period.
-
D.
languageOfOccupyingAuthorities
Indicates the language used by the authorities or powers that are occupying or controlling a territory.
-
E.
languageColonialAdministration
chosen
Indicates the language used by a colonial authority for governance, administration, and official functions over a 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: April 30, 2026, 11:48 p.m.