Triple
T36958074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Rest for the Living |
E914237
|
entity |
| Predicate | hasWADFileName |
P70988
|
FINISHED |
| Object | NERVE.WAD |
—
|
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: NERVE.WAD | Statement: [No Rest for the Living, hasWADFileName, NERVE.WAD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWADFileName Context triple: [No Rest for the Living, hasWADFileName, NERVE.WAD]
-
A.
containsIWAD
Indicates that one entity includes or holds an IWAD (Internal WAD file) within it.
-
B.
usesIWAD
Indicates that one entity employs or relies on a specific IWAD (Internal WAD file) as a required resource or base data set for its operation or content.
-
C.
hasDataFile
chosen
Indicates that an entity is associated with or linked to a specific data file that stores its related information.
-
D.
numberOfMegawads
Indicates the quantity of electrical power, measured in megawatts, associated with an entity or relationship.
-
E.
hasWarp
Indicates that one entity possesses, is equipped with, or is capable of using a warp or warp-related mechanism in relation to another entity or context.
- 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_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.