Triple
T33570340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Space |
E859879
|
entity |
| Predicate | interfaceDesign |
P180941
|
FINISHED |
| Object | diegetic HUD |
—
|
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: diegetic HUD | Statement: [Dead Space, interfaceDesign, diegetic HUD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interfaceDesign Context triple: [Dead Space, interfaceDesign, diegetic HUD]
-
A.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
B.
interfaceElements
chosen
Indicates a relationship where certain elements function as components or parts of a user or system interface.
-
C.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:40 a.m.