Triple
T11356609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onesimus |
E268968
|
entity |
| Predicate | PaulRefrainsFrom |
P4300
|
FINISHED |
| Object | keeping Onesimus without Philemon’s consent |
—
|
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: keeping Onesimus without Philemon’s consent | Statement: [Onesimus, PaulRefrainsFrom, keeping Onesimus without Philemon’s consent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaulRefrainsFrom Context triple: [Onesimus, PaulRefrainsFrom, keeping Onesimus without Philemon’s consent]
-
A.
refrain
Indicates that an entity deliberately holds back from performing a particular action or behavior.
-
B.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
C.
penaltyForRefusalOfOath
Indicates that a penalty is imposed on an entity for refusing to take a required oath.
-
D.
doesNotAbolish
Indicates that one entity, action, or law does not eliminate, revoke, or put an end to another.
-
E.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.