Triple
T3340336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saguia el-Hamra |
E70241
|
entity |
| Predicate | colonialNameLanguage |
P16846
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Saguia el-Hamra, colonialNameLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialNameLanguage Context triple: [Saguia el-Hamra, colonialNameLanguage, Spanish]
-
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
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
colonialExonymSource
chosen
Indicates that a name or term is derived from, or originates in, a colonial-era exonym imposed by an external colonial power.
-
D.
colonialPowerOfOrigin
Indicates the colonial state or empire from which a colony or formerly colonized territory originated or was governed.
-
E.
formerColonyName
Indicates that one entity is the historical or previous name used for a colony that later changed its political status or designation.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bf1f648190993ac8e9dda60983 |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.