Triple
T25979005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Christophe |
E646018
|
entity |
| Predicate | otherColonialPowerOnIsland |
P3075
|
FINISHED |
| Object | Great Britain |
—
|
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: Great Britain | Statement: [Saint-Christophe, otherColonialPowerOnIsland, Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherColonialPowerOnIsland Context triple: [Saint-Christophe, otherColonialPowerOnIsland, Great Britain]
-
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.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
D.
isColonialFoundationOf
Indicates that one entity was established as a colony that later developed into or served as the origin of the other entity.
-
E.
foundedAsColonyOf
Indicates that an entity was originally established as a colony under the control or authority 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 8:53 a.m.