Triple
T1186354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judas Iscariot |
E25255
|
entity |
| Predicate | returnedMoneyAccordingToMatthew |
P11352
|
FINISHED |
| Object | thirty pieces of silver |
—
|
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: thirty pieces of silver | Statement: [Judas Iscariot, returnedMoneyAccordingToMatthew, thirty pieces of silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedMoneyAccordingToMatthew Context triple: [Judas Iscariot, returnedMoneyAccordingToMatthew, thirty pieces of silver]
-
A.
returnedBy
chosen
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
B.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
C.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
D.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
E.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.