Triple
T37012373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escape from Wolfenstein |
E915983
|
entity |
| Predicate | includesBossLevel |
P86453
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Escape from Wolfenstein, includesBossLevel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBossLevel Context triple: [Escape from Wolfenstein, includesBossLevel, true]
-
A.
numberOfBosses
Indicates the count of distinct boss or supervisor entities associated with a given entity.
-
B.
requiresBossFight
Indicates that completing or progressing past a certain point necessitates defeating a designated boss character in combat.
-
C.
hasBossFights
chosen
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
D.
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.
-
E.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.