Triple
T14921227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedro Bay, Alaska |
E371512
|
entity |
| Predicate | nativeVillageStatus |
P45139
|
FINISHED |
| Object | federally recognized tribe |
—
|
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: federally recognized tribe | Statement: [Pedro Bay, Alaska, nativeVillageStatus, federally recognized tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeVillageStatus Context triple: [Pedro Bay, Alaska, nativeVillageStatus, federally recognized tribe]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
humanSettlementStatus
chosen
Indicates the classification of a place in terms of its status as a human settlement (e.g., whether and how it is recognized or designated as a populated place).
-
C.
hasNearbyTraditionalVillage
Indicates that an entity is located close to or in the vicinity of a traditional village.
-
D.
hasVillageAccess
Indicates that an entity is permitted to enter, use, or benefit from the facilities, services, or areas of a particular village.
-
E.
isInVillage
Indicates that one entity is located within or belongs to the area defined as a village in relation to another 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded63121e48190b54eb2546acc3c93 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:34 a.m.