Triple
T20517161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominican |
E503709
|
entity |
| Predicate | associatedColonialHistory |
P59372
|
FINISHED |
| Object | former Spanish colony |
—
|
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: former Spanish colony | Statement: [Dominican, associatedColonialHistory, former Spanish colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedColonialHistory Context triple: [Dominican, associatedColonialHistory, former Spanish colony]
-
A.
colonialHistoryIncludes
Indicates that one entity’s colonial history encompasses, involves, or includes the other entity as part of its colonial past.
-
B.
hasColonialHistory
chosen
Indicates that an entity has experienced or participated in a period of colonial rule, control, or administration in relation to another entity.
-
C.
previousColonialInvolvement
Indicates that one entity had a colonial role or presence in another entity at some time in the past.
-
D.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
E.
foundedInColonialEra
Indicates that the entity was established or came into existence during a historical period of colonial rule.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f42db688190a3ccfba5601e8bf3 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.