Triple
T36974926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venda bantustan |
E914671
|
entity |
| Predicate | declaredIndependent |
P164389
|
FINISHED |
| Object | 13 September 1979 |
—
|
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: 13 September 1979 | Statement: [Venda bantustan, declaredIndependent, 13 September 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredIndependent Context triple: [Venda bantustan, declaredIndependent, 13 September 1979]
-
A.
isIndependent
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
B.
hasIndependent
Indicates that one entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
C.
declaredIndependentBySouthAfrica
chosen
Indicates that an entity achieved independence through a formal declaration made by South Africa.
-
D.
originallyIndependentOf
Indicates that one entity was initially separate from, and not derived from or influenced by, another entity at the outset.
-
E.
organizedIndependentlyOf
Indicates that an entity was organized or formed without direction, control, or coordination from another specified entity.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.