Triple
T28667046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Cthulhu role-playing game |
E725610
|
entity |
| Predicate | notableAdventure |
P203315
|
FINISHED |
| Object | The Haunting |
—
|
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: The Haunting | Statement: [Call of Cthulhu role-playing game, notableAdventure, The Haunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAdventure Context triple: [Call of Cthulhu role-playing game, notableAdventure, The Haunting]
-
A.
hasAdventureOn
Indicates that an entity participates in or experiences an adventure that takes place on or during a specified context, such as a time, location, or medium.
-
B.
hasPerilousAdventure
Indicates that an entity experiences, undertakes, or is involved in a dangerous or high-risk adventure.
-
C.
notableDungeon
Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
-
D.
notableExpeditionLocation
Indicates that a location is a significant or primary place associated with a particular expedition.
-
E.
hasAdventureAt
Indicates that an entity experiences, undertakes, or is involved in an adventure at a specified location or setting.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0154b16a3c8190b808a460ae3a91ac |
completed | May 11, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a01539f19d88190b2de63f5262b1074 |
completed | May 11, 2026, 3:57 a.m. |
| PDg | Predicate description generation | batch_6a0154b0a9e48190ae747136b4587ceb |
completed | May 11, 2026, 4:01 a.m. |
Created at: April 28, 2026, 5:01 a.m.