Triple
T37512711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser Evils |
E932554
|
entity |
| Predicate | powerLevelComparedTo |
P193100
|
FINISHED |
| Object | less powerful than Prime Evils |
—
|
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: less powerful than Prime Evils | Statement: [Lesser Evils, powerLevelComparedTo, less powerful than Prime Evils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerLevelComparedTo Context triple: [Lesser Evils, powerLevelComparedTo, less powerful than Prime Evils]
-
A.
powerLevel
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.
powerLevelComparedToValar
Indicates how an entity’s power or strength compares relative to that of the Valar.
-
D.
powerLevelInStory
Indicates the relative strength or power a character or entity possesses within the context of a specific story or narrative.
-
E.
deFactoPowerLevel
Indicates the actual, effective level of power or control an entity holds in practice, regardless of its formal or official status.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4:17 p.m.