Triple
T37551085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | includesPvPStyleEncounter |
P205976
|
FINISHED |
| Object | Faction Champions |
E2232920
|
NE 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: Faction Champions | Statement: [Trial of the Crusader, includesPvPStyleEncounter, Faction Champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPvPStyleEncounter Context triple: [Trial of the Crusader, includesPvPStyleEncounter, Faction Champions]
-
A.
bossEncounterStyle
Indicates how a boss is confronted or engaged during an encounter, such as the manner, format, or mechanics of the battle.
-
B.
hasPvEContent
Indicates that something includes or provides player-versus-environment (PvE) gameplay content.
-
C.
hasPvPArea
Indicates that a location or zone is designated for player-versus-player (PvP) interactions or combat.
-
D.
requiresBossFight
Indicates that completing or progressing past a certain point necessitates defeating a designated boss character in combat.
-
E.
hasBossFights
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
- F. None of above. chosen
Provenance (5 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7ec19c0819085d68adc48bf3ed9 |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.