Triple
T9066974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadendoa |
E217267
|
entity |
| Predicate | colonialEraDesignation |
P42435
|
FINISHED |
| Object | tribe |
—
|
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: tribe | Statement: [Hadendoa, colonialEraDesignation, tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialEraDesignation Context triple: [Hadendoa, colonialEraDesignation, tribe]
-
A.
colonialEraClassification
Indicates how entities are categorized or labeled according to systems or standards established during a colonial historical period.
-
B.
colonialDesignation
chosen
Indicates that one entity assigns or holds a status, name, or classification for another entity within a colonial or colonially imposed framework.
-
C.
colonialEraStatus
Indicates the status or condition an entity held specifically during a colonial historical period.
-
D.
foundedInColonialEra
Indicates that the entity was established or came into existence during a historical period of colonial rule.
-
E.
periodOfColonialRule
Indicates the time span during which one political power exercised colonial control over another territory or people.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bde9c08190a4f568fbccc3c3e9 |
completed | April 1, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.