Triple
T37551124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Obsidian Sanctum |
E933591
|
entity |
| Predicate | hasOptionalBosses |
P188259
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [The Obsidian Sanctum, hasOptionalBosses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOptionalBosses Context triple: [The Obsidian Sanctum, hasOptionalBosses, yes]
-
A.
hasBossFights
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
B.
optionalBoss
chosen
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
C.
optionalBossMode
Indicates that an entity can optionally assume a boss or leadership role, but is not required to do so.
-
D.
numberOfBosses
Indicates the count of distinct boss or supervisor entities associated with a given entity.
-
E.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
- 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:17 p.m.