Triple
T6591510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colony of Natal |
E159370
|
entity |
| Predicate | grantedResponsibleGovernment |
P5083
|
FINISHED |
| Object | 1893 |
—
|
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: 1893 | Statement: [Colony of Natal, grantedResponsibleGovernment, 1893]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedResponsibleGovernment Context triple: [Colony of Natal, grantedResponsibleGovernment, 1893]
-
A.
grantedConstitution
Indicates that an authority formally bestowed or established a constitution for a political entity or organization.
-
B.
formedGovernmentWith
Indicates that two or more political entities joined together to establish or lead a government in partnership.
-
C.
grantsOfAutonomy
chosen
Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
-
D.
governmentInPowerAtEnactment
Indicates that a specific government or administration was the one holding power at the time a particular law, policy, or measure was enacted.
-
E.
intendedToGovern
Indicates that one entity was meant or designated to exercise authority or control over another entity or group.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.