Triple
T28287503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snohomish Tribe |
E713324
|
entity |
| Predicate | hasClanOrVillageStructure |
P4011
|
FINISHED |
| Object | village-based social organization |
—
|
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: village-based social organization | Statement: [Snohomish Tribe, hasClanOrVillageStructure, village-based social organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanOrVillageStructure Context triple: [Snohomish Tribe, hasClanOrVillageStructure, village-based social organization]
-
A.
hasClanOrBandStructure
Indicates that an entity is organized into, or participates in, a social structure based on clans or bands.
-
B.
hasClanChiefResidence
Indicates that a clan has the location where its chief resides or maintains an official dwelling.
-
C.
hasColonyStructure
Indicates that an entity exhibits an organized colony form or structural arrangement characteristic of colonial living.
-
D.
hasClanTerritory
Indicates that a clan possesses or controls a specific geographic territory as its domain.
-
E.
hasVillage
chosen
Indicates that an entity possesses, contains, or is associated with a village.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 11:27 p.m.