Triple
T6186979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klallam (S’Klallam) peoples |
E138084
|
entity |
| Predicate | notableCraft |
P5963
|
FINISHED |
| Object | cedar plank houses |
—
|
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: cedar plank houses | Statement: [Klallam (S’Klallam) peoples, notableCraft, cedar plank houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCraft Context triple: [Klallam (S’Klallam) peoples, notableCraft, cedar plank houses]
-
A.
traditionalCraft
chosen
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
B.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
C.
notableApprentice
Indicates that one entity is a distinguished or noteworthy apprentice of another entity.
-
D.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
E.
craftGuild
Indicates that an entity is a member of, affiliated with, or governed by a particular craft guild organization.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0621671988190938dd16242a2e4d5 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.