Triple
T212060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sirhan Sirhan |
E4741
|
entity |
| Predicate | convictionStatus |
P7958
|
FINISHED |
| Object | convicted |
—
|
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: convicted | Statement: [Sirhan Sirhan, convictionStatus, convicted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convictionStatus Context triple: [Sirhan Sirhan, convictionStatus, convicted]
-
A.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
B.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
C.
criminalStatus
chosen
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
-
D.
numberOfConvictions
Indicates the count of times an entity has been formally found guilty of an offense.
-
E.
prosecuted
Indicates that legal authorities have formally brought criminal charges against an entity and pursued a case against them in a court of law.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b4f71b88190866c8262922ae204 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.