Triple
T20931309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siyavash |
E515476
|
entity |
| Predicate | provesInnocenceBy |
P141732
|
FINISHED |
| Object | trial by fire |
—
|
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: trial by fire | Statement: [Siyavash, provesInnocenceBy, trial by fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provesInnocenceBy Context triple: [Siyavash, provesInnocenceBy, trial by fire]
-
A.
worksToProveInnocenceOf
Indicates that one entity actively engages in efforts or actions aimed at demonstrating or establishing the innocence of another entity.
-
B.
actuallyInnocentOf
Indicates that an entity is truly not responsible for or did not commit the action, offense, or wrongdoing in question, regardless of prior accusations or judgments.
-
C.
acquittedBy
Indicates that an entity was formally cleared of charges or blame through a decision or judgment made by another entity.
-
D.
acquittedOf
Indicates that an authority has formally cleared an entity of a specific charge, accusation, or wrongdoing.
-
E.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
- F. None of above. chosen
Provenance (4 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f6557e4881909ce932c3f538304a |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:49 p.m.