Triple
T9182397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarun |
E220363
|
entity |
| Predicate | responseToAdmonition |
P27820
|
FINISHED |
| Object | claimed his wealth was due to his own knowledge |
—
|
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: claimed his wealth was due to his own knowledge | Statement: [Qarun, responseToAdmonition, claimed his wealth was due to his own knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseToAdmonition Context triple: [Qarun, responseToAdmonition, claimed his wealth was due to his own knowledge]
-
A.
responseToWarning
Indicates how an entity reacts or behaves in consequence to a prior warning.
-
B.
reactionToAccusation
Indicates how an entity responds or behaves when confronted with an accusation made by another entity.
-
C.
usesGuidelines
Indicates that one entity follows or applies a specified set of guidelines in performing an action or making decisions.
-
D.
ruleIssue
Indicates that an authority or governing body formally creates, announces, or enacts a rule, regulation, or directive.
-
E.
ignoredAdviceOf
chosen
Indicates that one entity did not follow or act upon the advice given 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.