Triple
T38478212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thy Flesh Consumed |
E915601
|
entity |
| Predicate | containsSecretLevel |
P202374
|
FINISHED |
| Object | E4M9: Fear |
—
|
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: E4M9: Fear | Statement: [Thy Flesh Consumed, containsSecretLevel, E4M9: Fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSecretLevel Context triple: [Thy Flesh Consumed, containsSecretLevel, E4M9: Fear]
-
A.
hasSecretLevel
Indicates that an entity is associated with a particular secrecy or security classification level.
-
B.
hasSecretLevels
chosen
Indicates that an entity (such as a game) contains hidden or non-obvious levels that are not part of the standard progression.
-
C.
hasTypeOfSecrecy
Indicates that something is associated with a particular kind or level of secrecy.
-
D.
securityLevelsInclude
Indicates that one entity’s defined security levels contain or encompass the security levels of another entity.
-
E.
canBeSecret
Indicates that something has the potential or suitability to be kept hidden or confidential from others.
- 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_6a021f84715881908e25b6548e7cf62e |
completed | May 11, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_6a021739b7288190a4ca94c04074c78a |
completed | May 11, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.