Triple
T36957630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Schabbs |
E914227
|
entity |
| Predicate | hasBossMusic |
P139081
|
FINISHED |
| Object | unique boss theme in Wolfenstein 3D |
—
|
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: unique boss theme in Wolfenstein 3D | Statement: [Dr. Schabbs, hasBossMusic, unique boss theme in Wolfenstein 3D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBossMusic Context triple: [Dr. Schabbs, hasBossMusic, unique boss theme in Wolfenstein 3D]
-
A.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
B.
hasBossTheme
chosen
Indicates that an entity is associated with a special theme or music track specifically used during boss encounters or major confrontations.
-
C.
hasBossForm
Indicates that an entity has a special, typically more powerful "boss" version or transformation form.
-
D.
hasCentralBoss
Indicates that an entity is under the authority or control of a primary, central boss figure.
-
E.
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.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:13 p.m.