Triple
T30741180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the brother of Jared |
E782692
|
entity |
| Predicate | receivedDivineFavor |
P149000
|
FINISHED |
| Object | language not confounded |
—
|
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: language not confounded | Statement: [the brother of Jared, receivedDivineFavor, language not confounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedDivineFavor Context triple: [the brother of Jared, receivedDivineFavor, language not confounded]
-
A.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
B.
receivesBoon
chosen
Indicates that one entity is the beneficiary of a boon, gift, or advantageous favor provided by another entity or source.
-
C.
grantedBoonTo
Indicates that one entity has bestowed a favor, benefit, or special privilege upon another entity.
-
D.
blessedWith
Indicates that one entity has received a positive gift, talent, quality, or advantage attributed to another source.
-
E.
divineStatus
Indicates that an entity possesses a sacred, godlike, or religiously exalted status in relation to another entity or within a given belief system.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 8:38 p.m.