Triple
T27605624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingram family |
E700170
|
entity |
| Predicate | hasNotableLegalCase |
P3010
|
FINISHED |
| Object | Paul Ingram satanic ritual abuse case |
—
|
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: Paul Ingram satanic ritual abuse case | Statement: [Ingram family, hasNotableLegalCase, Paul Ingram satanic ritual abuse case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLegalCase Context triple: [Ingram family, hasNotableLegalCase, Paul Ingram satanic ritual abuse case]
-
A.
hasOngoingLegalSignificance
Indicates that a legal matter, status, or decision continues to have current relevance, effect, or consequences under the law.
-
B.
hasNotableIncident
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
C.
defendantInNotableTrial
Indicates that an entity served as the defendant in a trial that is considered notable or historically significant.
-
D.
hasLegalProceeding
chosen
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
E.
notableLawyer
Indicates that the subject is a lawyer who is distinguished or well-known for their legal work or reputation.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: April 27, 2026, 2:09 p.m.