Triple
T9535350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diotrephes |
E229999
|
entity |
| Predicate | refusesToWelcome |
P31766
|
FINISHED |
| Object | traveling Christian missionaries |
—
|
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: traveling Christian missionaries | Statement: [Diotrephes, refusesToWelcome, traveling Christian missionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusesToWelcome Context triple: [Diotrephes, refusesToWelcome, traveling Christian missionaries]
-
A.
refusesFurtherHelpTo
Indicates that one entity declines to provide any additional assistance or support to another entity.
-
B.
doesNotAccept
chosen
Indicates that one entity refuses, rejects, or is not configured to receive or allow something from another entity.
-
C.
typicallyDenies
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another entity.
-
D.
refusedAction
Indicates that an entity deliberately declined or did not agree to perform a specific action requested, expected, or proposed by another entity.
-
E.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98cc58bc8190ba921410e4b64aaa |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.