Triple
T28722127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Obed Marsh |
E730123
|
entity |
| Predicate | causeOfInnsmouthTransformation |
P175332
|
FINISHED |
| Object | pact with the Deep Ones |
—
|
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: pact with the Deep Ones | Statement: [Captain Obed Marsh, causeOfInnsmouthTransformation, pact with the Deep Ones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfInnsmouthTransformation Context triple: [Captain Obed Marsh, causeOfInnsmouthTransformation, pact with the Deep Ones]
-
A.
wasTurnedIntoVampireBy
Indicates that one entity became a vampire as a direct result of another entity’s actions.
-
B.
motherTransformedInto
Indicates that an entity’s mother has been changed or converted into another form, state, or entity.
-
C.
turnedIntoWerewolfBy
Indicates that one entity was transformed into a werewolf as a result of the actions or influence of another entity.
-
D.
turnedIntoVampireIn
Indicates that an entity became a vampire at or within a specified place or context.
-
E.
causeOfSupernaturalStatus
chosen
Indicates that one entity is the reason or source for another entity acquiring a supernatural state, condition, or power.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 5:54 a.m.