Triple
T2737023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugpiaq people |
E60652
|
entity |
| Predicate | modernResidence |
P75
|
FINISHED |
| Object | Kodiak Island communities |
—
|
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: Kodiak Island communities | Statement: [Sugpiaq people, modernResidence, Kodiak Island communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernResidence Context triple: [Sugpiaq people, modernResidence, Kodiak Island communities]
-
A.
residence
chosen
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
C.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
D.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb12e03c8190b270c814ce47b626 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.