Triple
T8916792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuska |
E212312
|
entity |
| Predicate | typeOfFireDeity |
P9989
|
FINISHED |
| Object | domestic and ritual fire god |
—
|
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: domestic and ritual fire god | Statement: [Nuska, typeOfFireDeity, domestic and ritual fire god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFireDeity Context triple: [Nuska, typeOfFireDeity, domestic and ritual fire god]
-
A.
typeOfDeity
chosen
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
B.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
C.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
D.
fireSymbolizes
Indicates that the concept or element of fire is used to represent, signify, or stand for another idea, quality, or meaning in a symbolic way.
-
E.
hasEternalFlame
Indicates that an entity possesses or maintains a flame that is intended to burn perpetually without being extinguished.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6610cd48819090a184c5f9465626 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.