Triple
T6591524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colony of Natal |
E159370
|
entity |
| Predicate | annexedByUnitedKingdom |
P960
|
FINISHED |
| Object | 1843 |
—
|
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: 1843 | Statement: [Colony of Natal, annexedByUnitedKingdom, 1843]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexedByUnitedKingdom Context triple: [Colony of Natal, annexedByUnitedKingdom, 1843]
-
A.
annexedBy
chosen
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
B.
countryAnnexedBy
Indicates that a country has been taken over and incorporated into the territory of another state through annexation.
-
C.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
D.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
E.
wasUnderTrusteeshipOf
Indicates that one entity was administered, overseen, or managed under the legal or formal trusteeship authority of another 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_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.