Triple
T17912621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinestro |
E447849
|
entity |
| Predicate | turnedVillainBecause |
P129295
|
FINISHED |
| Object | authoritarian rule of Korugar |
—
|
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: authoritarian rule of Korugar | Statement: [Sinestro, turnedVillainBecause, authoritarian rule of Korugar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnedVillainBecause Context triple: [Sinestro, turnedVillainBecause, authoritarian rule of Korugar]
-
A.
focusesOnVillain
Indicates that the primary attention, narrative emphasis, or activity is directed toward a villain as the central subject.
-
B.
turnedIntoVampireIn
Indicates that an entity became a vampire at or within a specified place or context.
-
C.
protagonistTransformation
Indicates a change or evolution that the main character undergoes, typically altering their traits, beliefs, or role over the course of a narrative.
-
D.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
E.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30288ac8190bc633e69447709bf |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db77df0c819084548168c62b398c |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:19 a.m.