Triple
T37464611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Explorers vs. League of E.V.I.L. |
E931002
|
entity |
| Predicate | hasVillainFaction |
P53524
|
FINISHED |
| Object | League of E.V.I.L. |
—
|
NE NERFINISHED |
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: League of E.V.I.L. | Statement: [League of Explorers vs. League of E.V.I.L., hasVillainFaction, League of E.V.I.L.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillainFaction Context triple: [League of Explorers vs. League of E.V.I.L., hasVillainFaction, League of E.V.I.L.]
-
A.
hasVillainFactionClasses
Indicates that certain classes or categories are associated with, or belong to, a villainous faction.
-
B.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
C.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
D.
hasOpposingFaction
chosen
Indicates that one faction stands in opposition or conflict to another faction.
-
E.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:17 p.m.