Triple
T27250995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Kongo |
E687483
|
entity |
| Predicate | colonialSuccessorState |
P59886
|
FINISHED |
| Object | Portuguese Angola |
—
|
NE NERFINISHED |
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: Portuguese Angola | Statement: [Kingdom of Kongo, colonialSuccessorState, Portuguese Angola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialSuccessorState Context triple: [Kingdom of Kongo, colonialSuccessorState, Portuguese Angola]
-
A.
successorColony
chosen
Indicates that one colony directly follows and replaces another colony as its historical or political successor.
-
B.
colonialOutcome
Indicates the result or consequence of a colonial relationship or process between entities.
-
C.
successorTerritorialStatus
Indicates the territorial status or jurisdiction that directly follows and replaces a previous territorial status in a succession or transition.
-
D.
associatedWithSuccessorColonialPower
Indicates a relationship where an entity is linked or connected to a later colonial authority that succeeded a previous colonial power.
-
E.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 10:45 a.m.