Triple
T36575435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipibo-Conibo people |
E902235
|
entity |
| Predicate | craftProduction |
P98026
|
FINISHED |
| Object | ceramics |
—
|
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: ceramics | Statement: [Shipibo-Conibo people, craftProduction, ceramics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftProduction Context triple: [Shipibo-Conibo people, craftProduction, ceramics]
-
A.
craftedIn
Indicates that an object or work was created or produced at a particular place or within a specific location.
-
B.
craftProcess
Indicates the method or sequence of actions used to create, shape, or assemble something, typically by skilled or artisanal means.
-
C.
craftEconomy
Indicates an economic relationship where goods or value are produced, exchanged, or sustained through crafting activities or artisanal production.
-
D.
craftSpecialty
chosen
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.