Triple
T31306393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee traditional religion |
E798344
|
entity |
| Predicate | hasSacredColor |
P90530
|
FINISHED |
| Object | red |
—
|
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: red | Statement: [Cherokee traditional religion, hasSacredColor, red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredColor Context triple: [Cherokee traditional religion, hasSacredColor, red]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
sacredColor
chosen
Indicates that a particular color is regarded as holy, revered, or religiously significant in relation to an entity or context.
-
C.
hasSacredNumber
Indicates that a particular number is regarded as sacred, holy, or spiritually significant in relation to an entity.
-
D.
hasSacredImage
Indicates that one entity possesses or is associated with an image regarded as sacred or religiously significant.
-
E.
hasSacredWeapon
Indicates that an entity possesses or is associated with a weapon regarded as holy, consecrated, or religiously significant.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 9:14 p.m.