Triple
T36957600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Schabbs |
E914227
|
entity |
| Predicate | introducedInVideoGame |
P183495
|
FINISHED |
| Object | Wolfenstein 3D |
—
|
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: Wolfenstein 3D | Statement: [Dr. Schabbs, introducedInVideoGame, Wolfenstein 3D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInVideoGame Context triple: [Dr. Schabbs, introducedInVideoGame, Wolfenstein 3D]
-
A.
introducedInGameAs
chosen
Indicates that an entity first appeared or was made available within a specific game title.
-
B.
appearedInVideoGame
Indicates that an entity is featured as a character, element, or content within a specific video game.
-
C.
introducedToGame
Indicates that one entity caused or facilitated another entity’s initial exposure or introduction to a particular game.
-
D.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
E.
introducedInGameRegion
Indicates that something first appeared or was made available within a specific region of a game.
- 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_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:13 p.m.