Triple
T37551061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | thirdBoss |
P126648
|
FINISHED |
| Object | Faction Champions |
—
|
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: Faction Champions | Statement: [Trial of the Crusader, thirdBoss, Faction Champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdBoss Context triple: [Trial of the Crusader, thirdBoss, Faction Champions]
-
A.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
B.
stageBossOf
chosen
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
C.
finalBossOf
Indicates that one entity serves as the ultimate or last major opponent or challenge that another entity must face or overcome.
-
D.
dropBoss
Indicates that one entity dismisses, removes, or ceases to support another entity who holds a position of authority or leadership.
-
E.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:17 p.m.