Triple
T11929549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitimacha |
E283873
|
entity |
| Predicate | materialUsedInBasketry |
P1272
|
FINISHED |
| Object | river cane |
—
|
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: river cane | Statement: [Chitimacha, materialUsedInBasketry, river cane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialUsedInBasketry Context triple: [Chitimacha, materialUsedInBasketry, river cane]
-
A.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
usesFolkMaterial
Indicates that one entity incorporates or draws upon traditional folk materials, such as melodies, stories, or motifs, in relation to another entity.
-
C.
traditionalMaterial
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
D.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
-
E.
collectsMaterialType
Indicates that an entity gathers or acquires materials of a specified type.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.