Triple
T26012223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suamox |
E646930
|
entity |
| Predicate | colonialNameDerivedAs |
P13172
|
FINISHED |
| Object | Sogamoso |
—
|
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: Sogamoso | Statement: [Suamox, colonialNameDerivedAs, Sogamoso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialNameDerivedAs Context triple: [Suamox, colonialNameDerivedAs, Sogamoso]
-
A.
colonialNameUsedBy
Indicates that a colonial-era name for a place, group, or entity is used or applied by a particular agent or source.
-
B.
hasColonialName
chosen
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
preColonialNameFor
Indicates that one name was used for something in the pre-colonial period and refers to the same entity later known by a different (typically colonial or post-colonial) name.
-
D.
colonialExonymSource
Indicates that a name or term is derived from, or originates in, a colonial-era exonym imposed by an external colonial power.
-
E.
colonialOrigin
Indicates that one entity originates from, was established by, or is otherwise derived from the colonial presence or control of 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b5f34c8190880875cdd32ab051 |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 9:02 a.m.