Triple
T29213080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm-god of Hatti |
E740592
|
entity |
| Predicate | centralInMyth |
P4751
|
FINISHED |
| Object | Illuyanka myth |
—
|
NE NERFINISHED |
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: Illuyanka myth | Statement: [Storm-god of Hatti, centralInMyth, Illuyanka myth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralInMyth Context triple: [Storm-god of Hatti, centralInMyth, Illuyanka myth]
-
A.
centralMystery
Indicates that something serves as the primary unresolved question or puzzle around which a narrative, situation, or investigation is structured.
-
B.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralDeitySymbol
Indicates that one entity serves as the primary or central symbolic representation of a deity for another entity.
-
D.
mythologicalCapital
Indicates that a location serves as the principal or central city associated with a particular mythology or pantheon.
-
E.
centralConjecture
Indicates that the subject proposition is the main or most important conjecture around which related arguments, results, or discussions are organized.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 12:12 p.m.