Triple
T37551125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Obsidian Sanctum |
E933591
|
entity |
| Predicate | optionalBoss |
P188259
|
FINISHED |
| Object | Tenebron |
—
|
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: Tenebron | Statement: [The Obsidian Sanctum, optionalBoss, Tenebron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionalBoss Context triple: [The Obsidian Sanctum, optionalBoss, Tenebron]
-
A.
stageBossOf
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
B.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
C.
finalBossOf
Indicates that one entity serves as the ultimate or last major opponent or challenge that another entity must face or overcome.
-
D.
fictionalBossOf
Indicates a relationship where one entity is the boss or superior of another within a fictional or imagined context.
-
E.
subBossCharacter
Indicates that one character serves as a subordinate or secondary boss in relation to another character within a hierarchy.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.