Triple
T30106793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kur |
E765155
|
entity |
| Predicate | locatedInMythicCosmos |
P20384
|
FINISHED |
| Object | beneath the earth |
—
|
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: beneath the earth | Statement: [Kur, locatedInMythicCosmos, beneath the earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMythicCosmos Context triple: [Kur, locatedInMythicCosmos, beneath the earth]
-
A.
positionOnMyth
Indicates the relative stance or viewpoint an entity holds regarding a particular myth.
-
B.
hasMythicSetting
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
-
C.
mythologicalLocation
chosen
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
D.
hasMythologicalInhabitant
Indicates that a place or location is traditionally believed to be inhabited or occupied by a mythological being or creature.
-
E.
builtLocationInUniverse
Indicates that a construction or structure was created or established at a specific location within a particular universe or cosmic setting.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: April 29, 2026, 7:09 p.m.