Triple
T13681499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraclete |
E328013
|
entity |
| Predicate | timeOfSending |
P1936
|
FINISHED |
| Object | after Jesus’ departure |
—
|
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: after Jesus’ departure | Statement: [Paraclete, timeOfSending, after Jesus’ departure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfSending Context triple: [Paraclete, timeOfSending, after Jesus’ departure]
-
A.
dateSent
Indicates the specific date on which something (such as a message, document, or item) was sent from one party to another.
-
B.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
-
C.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
time
chosen
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
intendedResponseTime
Indicates the expected or planned amount of time within which a response should be given or received.
- 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_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. |
Created at: April 9, 2026, 9:53 p.m.