Triple
T8082031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NunatuKavut Inuit |
E188637
|
entity |
| Predicate | mainSettlementRegion |
P59512
|
FINISHED |
| Object | south coast of Labrador |
—
|
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: south coast of Labrador | Statement: [NunatuKavut Inuit, mainSettlementRegion, south coast of Labrador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSettlementRegion Context triple: [NunatuKavut Inuit, mainSettlementRegion, south coast of Labrador]
-
A.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
B.
settledRegion
Indicates that an entity has established a lasting presence or habitation within a particular geographic region.
-
C.
traditionalSettlementArea
chosen
Indicates that an area is recognized as a traditional settlement zone associated with a particular group or community.
-
D.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
E.
capitalSettlementOfRegion
Indicates that a settlement serves as the administrative or political capital of a specified 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a699388190a5b8e26524ae43e5 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.