Triple
T31657592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jennifer Check |
E807898
|
entity |
| Predicate | causeOfPossession |
P184393
|
FINISHED |
| Object | failed virgin sacrifice |
—
|
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: failed virgin sacrifice | Statement: [Jennifer Check, causeOfPossession, failed virgin sacrifice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPossession Context triple: [Jennifer Check, causeOfPossession, failed virgin sacrifice]
-
A.
confiscatedBy
Indicates that something has been taken away and seized by an authority or agent, typically as a legal or disciplinary action.
-
B.
previouslyPossessedBy
Indicates that an entity was owned or possessed by another entity at some time in the past, but is not necessarily possessed by that entity now.
-
C.
reasonForAcquisition
Indicates the underlying purpose, motive, or justification for which one entity acquires another entity or asset.
-
D.
ownershipRecordedBy
Indicates that the fact or status of ownership of an entity is documented or registered by a particular agent or system.
-
E.
ownershipSince
Indicates the point in time from which an entity has continuously owned another entity.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 30, 2026, 10:56 p.m.