Triple
T38498464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Artis |
E919759
|
entity |
| Predicate | coConvictedWith |
P130403
|
FINISHED |
| Object | Rubin "Hurricane" Carter |
—
|
NE NERFINISHED |
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: Rubin "Hurricane" Carter | Statement: [John Artis, coConvictedWith, Rubin "Hurricane" Carter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coConvictedWith Context triple: [John Artis, coConvictedWith, Rubin "Hurricane" Carter]
-
A.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
B.
convictedAlongside
chosen
Indicates that one entity was convicted in a legal proceeding together with another entity as co-defendants in the same case or trial.
-
C.
someMembersConvictedOf
Indicates that within a group or organization, at least one member has been found guilty of a crime or offense through a formal legal or disciplinary process.
-
D.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
E.
numberOfConvictions
Indicates the count of times an entity has been formally found guilty of an offense.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.