Triple
T13681533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | healing of the paralytic at Bethesda |
E328014
|
entity |
| Predicate | associatedWithAccusation |
P111135
|
FINISHED |
| Object | Sabbath-breaking |
—
|
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: Sabbath-breaking | Statement: [healing of the paralytic at Bethesda, associatedWithAccusation, Sabbath-breaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAccusation Context triple: [healing of the paralytic at Bethesda, associatedWithAccusation, Sabbath-breaking]
-
A.
coAccusedInCaseWith
Indicates that two or more entities are jointly accused as defendants in the same legal case.
-
B.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
C.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
D.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
-
E.
victimOfAccusation
Indicates that an entity is the target or subject of an accusation made by another party.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.