Triple
T9182393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarun |
E220363
|
entity |
| Predicate | admonishedTo |
P488
|
FINISHED |
| Object | seek the Hereafter with what God gave him |
—
|
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: seek the Hereafter with what God gave him | Statement: [Qarun, admonishedTo, seek the Hereafter with what God gave him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admonishedTo Context triple: [Qarun, admonishedTo, seek the Hereafter with what God gave him]
-
A.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
B.
advises
chosen
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
C.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
D.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
-
E.
subjectOfCondemnation
Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc2553e548190898434aeda517407 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.