Triple
T29498354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsáchila people |
E748299
|
entity |
| Predicate | hairColoringSymbolism |
P74257
|
FINISHED |
| Object | protection and identity |
—
|
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: protection and identity | Statement: [Tsáchila people, hairColoringSymbolism, protection and identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairColoringSymbolism Context triple: [Tsáchila people, hairColoringSymbolism, protection and identity]
-
A.
starColorSymbolism
Indicates how the color of a star is associated with particular symbolic meanings or themes.
-
B.
primaryColorSymbolism
Indicates how a primary color is symbolically associated with particular meanings, emotions, or concepts in a given context.
-
C.
colorSymbolismBlack
Indicates the association or symbolic meaning attributed to the color black in a given context.
-
D.
colorInIconography
Indicates that a particular color is used to represent or symbolize an entity within a specific iconographic or symbolic tradition.
-
E.
hairAsSymbol
chosen
Indicates that hair functions as a symbolic element representing ideas, traits, or meanings beyond its literal physical presence.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c3129508190aa6bbd520f4daea6 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:20 p.m.