Triple
T37464610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Explorers vs. League of E.V.I.L. |
E931002
|
entity |
| Predicate | hasHeroFaction |
P196164
|
FINISHED |
| Object | League of Explorers |
—
|
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 Explorers | Statement: [League of Explorers vs. League of E.V.I.L., hasHeroFaction, League of Explorers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroFaction Context triple: [League of Explorers vs. League of E.V.I.L., hasHeroFaction, League of Explorers]
-
A.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
B.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
C.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
D.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
E.
hasVillainFactionClasses
Indicates that certain classes or categories are associated with, or belong to, a villainous faction.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
| PDg | Predicate description generation | batch_69fe0d14778c8190986fa4f37f992a2f |
completed | May 8, 2026, 4:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.