Triple
T1474183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calais |
E30799
|
entity |
| Predicate | wasEnglishPossessionUntil |
P6044
|
FINISHED |
| Object | 1558 |
—
|
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: 1558 | Statement: [Calais, wasEnglishPossessionUntil, 1558]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEnglishPossessionUntil Context triple: [Calais, wasEnglishPossessionUntil, 1558]
-
A.
wasColonialPower
Indicates that one entity historically exercised colonial control or dominance over another entity.
-
B.
broughtUnderBritishCrown
chosen
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
C.
usedByColonialPower
Indicates that something is employed or exploited as a tool, resource, or mechanism by a colonial power in the context of domination or control.
-
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.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6011d248190988380eca4ecf514 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.