Triple
T30032923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundhum |
E763071
|
entity |
| Predicate | recognizesDeityType |
P101789
|
FINISHED |
| Object | nature 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: nature spirits | Statement: [Mundhum, recognizesDeityType, nature spirits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesDeityType Context triple: [Mundhum, recognizesDeityType, nature spirits]
-
A.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
B.
representsDeity
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
-
C.
deityIdentification
chosen
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
-
D.
usedForDeityType
Indicates that something is employed or designated for use in connection with a particular type or category of deity.
-
E.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
- 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 6:50 p.m.