Triple
T7941283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conservative Party (South Africa) |
E184396
|
entity |
| Predicate | languageBase |
P11734
|
FINISHED |
| Object | Afrikaans-speaking population |
—
|
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: Afrikaans-speaking population | Statement: [Conservative Party (South Africa), languageBase, Afrikaans-speaking population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageBase Context triple: [Conservative Party (South Africa), languageBase, Afrikaans-speaking population]
-
A.
standardLanguageBasisFor
Indicates that one language serves as the normative or reference standard upon which another language variety, form, or usage is based.
-
B.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
C.
languageProvision
chosen
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
languageName
Indicates the specific name assigned to a language in the relationship.
-
E.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0ac8bc8190b4e4f79b15c316b3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.