Triple
T35026075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Space 2 |
E1010340
|
entity |
| Predicate | notableSuit |
P206814
|
FINISHED |
| Object | Engineering Suit |
—
|
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: Engineering Suit | Statement: [Dead Space 2, notableSuit, Engineering Suit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSuit Context triple: [Dead Space 2, notableSuit, Engineering Suit]
-
A.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
-
B.
notableTie
Indicates a significant connection or association between entities that is noteworthy or distinguished in some context.
-
C.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
- F. None of above. chosen
Provenance (4 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.