Triple
T27061576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shea Daniels |
E685057
|
entity |
| Predicate | hasCriminalBackground |
P167247
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shea Daniels, hasCriminalBackground, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriminalBackground Context triple: [Shea Daniels, hasCriminalBackground, yes]
-
A.
hasCriminalCharacter
Indicates that an entity possesses traits, behaviors, or a reputation associated with criminal activity or unlawful conduct.
-
B.
hasHadCriminalConviction
Indicates that an entity has previously been found guilty of a criminal offense through a legal process.
-
C.
hasLawEnforcementHistory
chosen
Indicates that an entity has a record of past involvement with law enforcement, such as prior incidents, investigations, or offenses.
-
D.
hasPerpetratorBackground
Indicates that an action, event, or crime is associated with information describing the background or history of its perpetrator.
-
E.
hasCriminalElement
Indicates that the subject involves, contains, or is associated with an illegal or criminal component, activity, or characteristic.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 8:22 a.m.