Triple
T30033198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yema |
E763078
|
entity |
| Predicate | spiritDomain |
P105130
|
FINISHED |
| Object | ancestral spirits |
—
|
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: ancestral spirits | Statement: [Yema, spiritDomain, ancestral spirits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritDomain Context triple: [Yema, spiritDomain, ancestral spirits]
-
A.
spiritCategory
Indicates that one entity is classified as belonging to a particular type or category of spirit.
-
B.
associatedSpirit
Indicates a relationship where one entity is linked to or accompanied by a particular spirit, often as a guide, protector, or defining supernatural presence.
-
C.
associatedSpiritCategory
chosen
Indicates that one entity is linked to another as the category or type under which a particular spirit or spiritual being is classified.
-
D.
typeOfSpirit
Indicates the specific kind or category of spirit (e.g., ghost, demon, angel) that an entity belongs to.
-
E.
primarySpirit
Indicates that one entity is the main or most fundamental spiritual essence 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d24a38819085259446e0d966c3 |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:50 p.m.