Triple
T11543544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning Hells |
E273728
|
entity |
| Predicate | loreType |
P99966
|
FINISHED |
| Object | cosmology element |
—
|
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: cosmology element | Statement: [Burning Hells, loreType, cosmology element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreType Context triple: [Burning Hells, loreType, cosmology element]
-
A.
historicalExploration
Indicates that an entity has engaged in or is associated with the act of exploring or investigating something in the past.
-
B.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
C.
areaTheme
Indicates that a particular theme, topic, or subject is associated with or characterizes a given area or region.
-
D.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
-
E.
loreSignificance
Indicates that something holds notable importance, relevance, or impact within a fictional world’s backstory, mythology, or overarching narrative.
- F. None of above. chosen
Provenance (4 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.