Triple
T18640086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eli |
E455660
|
entity |
| Predicate | receivedMessageFrom |
P113861
|
FINISHED |
| Object | man of God who prophesied judgment |
—
|
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: man of God who prophesied judgment | Statement: [Eli, receivedMessageFrom, man of God who prophesied judgment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedMessageFrom Context triple: [Eli, receivedMessageFrom, man of God who prophesied judgment]
-
A.
receivedRuleFrom
Indicates that one entity has obtained or been given a rule from another entity.
-
B.
receivedMarkFrom
Indicates that one entity has been given or assigned a mark, grade, or score by another entity.
-
C.
receivedTransmissionOf
chosen
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
D.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
E.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcbe3088190849f60b09d1e7e4b |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.