Triple
T2772861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugpiaq |
E61497
|
entity |
| Predicate | colonialContactPeriod |
P21862
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Sugpiaq, colonialContactPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialContactPeriod Context triple: [Sugpiaq, colonialContactPeriod, 18th century]
-
A.
colonialPeriodEnd
Indicates the time or event at which a colonial period or colonial rule over a territory comes to an end.
-
B.
periodOfColonialRule
chosen
Indicates the time span during which one political power exercised colonial control over another territory or people.
-
C.
colonialEraStatus
Indicates the status or condition an entity held specifically during a colonial historical period.
-
D.
usedInColonialPeriod
Indicates that something was utilized or in active use during a historical colonial period.
-
E.
colonialPowerAtFirstArrival
Indicates that a specified colonial power was the first to arrive and establish a presence or control in a given territory or region.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.