Triple
T28728343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Rookwood |
E730286
|
entity |
| Predicate | bossFightIn |
P126648
|
FINISHED |
| Object | Hogwarts Legacy |
—
|
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: Hogwarts Legacy | Statement: [Victor Rookwood, bossFightIn, Hogwarts Legacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossFightIn Context triple: [Victor Rookwood, bossFightIn, Hogwarts Legacy]
-
A.
bossBattlePhase
Indicates the specific stage or phase within a boss battle that an entity is currently engaged in.
-
B.
hasBossFights
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
C.
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.
-
D.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
E.
finalBossOf
Indicates that one entity serves as the ultimate or last major opponent or challenge that another entity must face or overcome.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657662cec8190b1cf4ec832658a3b |
completed | May 2, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:57 a.m.