Triple
T30597039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Chaos |
E778814
|
entity |
| Predicate | denotesPowerLevel |
P36248
|
FINISHED |
| Object | cosmic |
—
|
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: cosmic | Statement: [Lord of Chaos, denotesPowerLevel, cosmic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesPowerLevel Context triple: [Lord of Chaos, denotesPowerLevel, cosmic]
-
A.
powerLevel
chosen
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
B.
powerLevelVariesBy
Indicates that the power level of an entity changes depending on, or as a function of, another specified factor or context.
-
C.
supportsPowerLevel
Indicates that one entity is capable of providing or sustaining the required power level for another entity or operation.
-
D.
powerLevelInStory
Indicates the relative strength or power a character or entity possesses within the context of a specific story or narrative.
-
E.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:24 p.m.