Triple
T20604729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gitlaxt’aamiks |
E506273
|
entity |
| Predicate | isIndigenousSettlementType |
P140732
|
FINISHED |
| Object | First Nations village |
—
|
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: First Nations village | Statement: [Gitlaxt’aamiks, isIndigenousSettlementType, First Nations village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndigenousSettlementType Context triple: [Gitlaxt’aamiks, isIndigenousSettlementType, First Nations village]
-
A.
isAndeanSettlement
Indicates that a settlement is located in, or culturally associated with, the Andean region.
-
B.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
C.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
D.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
-
E.
isPartOfCommunalSettlementTradition
Indicates that something belongs to, or participates in, a shared tradition of communal settlement practices or ways of living together.
- F. None of above. chosen
Provenance (4 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa233e1881908749d2f29c2946e4 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.