Triple
T31306439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee traditional religion |
E798344
|
entity |
| Predicate | hasViewOnAnimals |
P187579
|
FINISHED |
| Object | animals as spiritual relatives |
—
|
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: animals as spiritual relatives | Statement: [Cherokee traditional religion, hasViewOnAnimals, animals as spiritual relatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnAnimals Context triple: [Cherokee traditional religion, hasViewOnAnimals, animals as spiritual relatives]
-
A.
usesLiveAnimals
Indicates that one entity employs or incorporates live animals in performing an action, service, process, or activity involving another entity.
-
B.
hasAnimal
Indicates that one entity possesses, keeps, or is associated with an animal.
-
C.
hasAnthropomorphicAnimals
Indicates that something features animals with human-like characteristics, behaviors, or roles.
-
D.
isAnimal
Indicates that the subject entity belongs to the category of animals (i.e., is an animal).
-
E.
usesAnimalCarcass
Indicates that an entity makes use of an animal’s dead body or its remains for some purpose.
- F. None of above. chosen
Provenance (4 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_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 29, 2026, 9:14 p.m.