Triple
T28479723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajdir |
E720656
|
entity |
| Predicate | opposedColonialPowers |
P16231
|
FINISHED |
| Object | Spain |
—
|
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: Spain | Statement: [Ajdir, opposedColonialPowers, Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedColonialPowers Context triple: [Ajdir, opposedColonialPowers, Spain]
-
A.
colonialPowerOpposed
chosen
Indicates that one colonial power actively resisted, conflicted with, or worked against another colonial power or its interests.
-
B.
originalColonialPowerOpposed
Indicates that the colonial power that originally controlled a territory actively opposed a particular event, change, or action related to that territory.
-
C.
colonialPowerInvolved
Indicates that a colonial power is involved in, influences, or exerts control over the referenced situation, event, or relationship.
-
D.
colonialPowerOnOtherSide
Indicates that one entity serves as the colonial ruling power over another entity located on the opposite or receiving side of a colonial relationship.
-
E.
colonialPowerInHistory
Indicates that one entity historically exercised colonial control, dominance, or governance over 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 2:54 a.m.