Triple
T20320328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woman taken in adultery |
E492190
|
entity |
| Predicate | actionByAccusers |
P139660
|
FINISHED |
| Object | bring woman before Jesus |
—
|
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: bring woman before Jesus | Statement: [Woman taken in adultery, actionByAccusers, bring woman before Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionByAccusers Context triple: [Woman taken in adultery, actionByAccusers, bring woman before Jesus]
-
A.
hasAccuser
Indicates that one entity serves as the accuser of another entity in a dispute, complaint, or allegation.
-
B.
outcomeForAccusers
Indicates the result or consequence experienced by the accusers as a result of a particular event, process, or decision.
-
C.
accuserIn
Indicates that one entity is the party who brings a charge or accusation against another entity within a specific context or case.
-
D.
coAccusedInCaseWith
Indicates that two or more entities are jointly accused as defendants in the same legal case.
-
E.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778b8b648190b80badaf15be2599 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:20 a.m.