Triple
T38478229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ultimate Doom |
E915602
|
entity |
| Predicate | addsContentBeyond |
P150602
|
FINISHED |
| Object | original Doom campaign |
—
|
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: original Doom campaign | Statement: [The Ultimate Doom, addsContentBeyond, original Doom campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsContentBeyond Context triple: [The Ultimate Doom, addsContentBeyond, original Doom campaign]
-
A.
extendsBeyond
Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
-
B.
addsOverBase
chosen
Indicates that something is added on top of an existing base amount, value, or structure.
-
C.
allowedContent
Indicates that certain content is permitted or acceptable within a given context, policy, or system.
-
D.
extendsBetween
Indicates a relationship where one entity spans or stretches from one point, object, or boundary to another, covering the space between them.
-
E.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.