Triple
T36863561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tualatin Kalapuya |
E911008
|
entity |
| Predicate | traditionalToolMaterial |
P127349
|
FINISHED |
| Object | wood |
—
|
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: wood | Statement: [Tualatin Kalapuya, traditionalToolMaterial, wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalToolMaterial Context triple: [Tualatin Kalapuya, traditionalToolMaterial, wood]
-
A.
traditionalMaterial
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
D.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
-
E.
materialUsedForInstruments
chosen
Indicates that a particular material is used in the construction or manufacture of one or more instruments.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:13 p.m.