Triple
T31657591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jennifer Check |
E807898
|
entity |
| Predicate | rituallySacrificedBy |
P168192
|
FINISHED |
| Object | Low Shoulder (the band) |
—
|
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: Low Shoulder (the band) | Statement: [Jennifer Check, rituallySacrificedBy, Low Shoulder (the band)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rituallySacrificedBy Context triple: [Jennifer Check, rituallySacrificedBy, Low Shoulder (the band)]
-
A.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
B.
sacrificedBy
chosen
Indicates that an entity has been given up, killed, or offered as a sacrifice by another entity.
-
C.
methodOfSacrifice
Indicates the specific way or procedure by which a sacrifice is carried out.
-
D.
sacrificialMedium
Indicates that one entity serves as the medium or vehicle through which another entity is sacrificed or offered.
-
E.
resultOfSacrifice
Indicates that something exists or occurs as the outcome or consequence of a sacrificial act.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:56 p.m.