Triple
T31692597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolai Wolf |
E808831
|
entity |
| Predicate | targetOfRitual |
P149215
|
FINISHED |
| Object | Jennifer Check |
—
|
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: Jennifer Check | Statement: [Nikolai Wolf, targetOfRitual, Jennifer Check]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfRitual Context triple: [Nikolai Wolf, targetOfRitual, Jennifer Check]
-
A.
hasRitualGoal
Indicates that an action, practice, or ritual is performed with the specific purpose of achieving a particular ritualistic outcome or objective.
-
B.
ritualsDirectedAt
chosen
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
C.
targetedDeity
Indicates that an action, event, or entity is specifically directed toward or aimed at a particular deity.
-
D.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
E.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 30, 2026, 11:09 p.m.