Triple
T38478086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shores of Hell |
E915599
|
entity |
| Predicate | hasFirstLevel |
P202519
|
FINISHED |
| Object | E2M1: Deimos Anomaly |
—
|
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: E2M1: Deimos Anomaly | Statement: [The Shores of Hell, hasFirstLevel, E2M1: Deimos Anomaly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstLevel Context triple: [The Shores of Hell, hasFirstLevel, E2M1: Deimos Anomaly]
-
A.
hasFirstLineUpperLevel
Indicates that an entity’s first line is located on or belongs to an upper-level section or tier within a larger structure or hierarchy.
-
B.
hasSecondLevel
Indicates that an entity possesses or is associated with a second hierarchical level within a structured system or classification.
-
C.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
-
D.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
-
E.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a008c77d4dc8190b342d7407eaf48fa |
completed | May 10, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_6a008c18531c8190bbe883b73e6d023f |
completed | May 10, 2026, 1:46 p.m. |
| PDg | Predicate description generation | batch_6a008c770df481908fe58b265fba06a3 |
completed | May 10, 2026, 1:47 p.m. |
Created at: May 3, 2026, 4:31 p.m.