Triple
T14315348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hachuamish |
E354940
|
entity |
| Predicate | nativeGroupOf |
P113935
|
FINISHED |
| Object | Seattle area of Washington State |
—
|
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: Seattle area of Washington State | Statement: [Hachuamish, nativeGroupOf, Seattle area of Washington State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeGroupOf Context triple: [Hachuamish, nativeGroupOf, Seattle area of Washington State]
-
A.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
B.
nativeOf
Indicates that an entity originates from or was born in a particular place, region, or country.
-
C.
servedNativeGroup
Indicates that one entity provided service, assistance, or work to a particular native or indigenous group.
-
D.
commonNameGroup
Indicates that multiple entities share the same commonly used name or are grouped under a single common name.
-
E.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8838e45c819080ee69dd39e3bd43 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:12 a.m.