Triple
T9663446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ifni enclave |
E233643
|
entity |
| Predicate | decolonizationIssue |
P89483
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ifni enclave, decolonizationIssue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decolonizationIssue Context triple: [Ifni enclave, decolonizationIssue, yes]
-
A.
decolonizationConflict
Indicates a conflict or struggle arising from the process of ending colonial rule and transferring power from a colonial authority to formerly colonized entities.
-
B.
decolonizationOutcome
Indicates the result or consequences that follow from a process of decolonization.
-
C.
decolonizationWave
Indicates a process or period in which territories or peoples transition from colonial rule to political independence or self-determination.
-
D.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
E.
postColonialReorganization
Indicates the restructuring or redefinition of political, social, or economic relationships following the end of colonial rule.
- F. None of above. chosen
Provenance (4 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0cde048190b5a8e1548825d4d9 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.