Triple
T23239377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebowa |
E581393
|
entity |
| Predicate | selfGovernmentGranted |
P5083
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Lebowa, selfGovernmentGranted, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfGovernmentGranted Context triple: [Lebowa, selfGovernmentGranted, 1972]
-
A.
grantsOfAutonomy
chosen
Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
-
B.
selfGoverning
Indicates that an entity has the authority and capacity to govern, regulate, and manage itself independently, without external control.
-
C.
independenceGranted
Indicates that one entity has formally conferred political or operational autonomy to another entity, ending or reducing prior control or dependency.
-
D.
selfGovernedBy
Indicates that an entity independently controls and manages itself without external governance.
-
E.
governingBodyHistoricallyGrantedBy
Indicates that the authority or power of a governing body was originally conferred or established by a specified entity or source in the past.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ebaef4819083a7805537ad993f |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.