Triple
T25305552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avikam people |
E634470
|
entity |
| Predicate | countryFormerColonialPower |
P3075
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Avikam people, countryFormerColonialPower, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryFormerColonialPower Context triple: [Avikam people, countryFormerColonialPower, France]
-
A.
wasColonialPower
chosen
Indicates that one entity historically exercised colonial control or dominance over another entity.
-
B.
partOfColonialEntity
Indicates that one entity is a constituent or subordinate territorial unit within a larger colonial political or administrative entity.
-
C.
countryUsingBeforeIndependence
Indicates that an entity was used or in effect in a particular country prior to that country’s independence.
-
D.
formerColonyName
Indicates that one entity is the historical or previous name used for a colony that later changed its political status or designation.
-
E.
colonialPowerOfOrigin
Indicates the colonial state or empire from which a colony or formerly colonized territory originated or was governed.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 1:25 p.m.