Triple
T24218468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Sulawesi ethnic groups |
E601372
|
entity |
| Predicate | hasTraditionalTextiles |
P132805
|
FINISHED |
| Object | ikat weaving |
—
|
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: ikat weaving | Statement: [South Sulawesi ethnic groups, hasTraditionalTextiles, ikat weaving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalTextiles Context triple: [South Sulawesi ethnic groups, hasTraditionalTextiles, ikat weaving]
-
A.
textileFeature
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
B.
textileType
Indicates the specific kind or category of textile material associated with an entity.
-
C.
hasTraditionalColors
Indicates that an entity is associated with colors that are traditionally or customarily linked to it.
-
D.
usesDesignTradition
Indicates that one entity creates, interprets, or operates according to the established design principles, styles, or conventions associated with another entity or tradition.
-
E.
typicalWeavingTechnique
chosen
Indicates that one entity is the characteristic or commonly used weaving method associated with another entity.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820a80ec8190bd11f08f7733843d |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.