Triple
T22388710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie Horton |
E553460
|
entity |
| Predicate | issueFramedAs |
P147462
|
FINISHED |
| Object | crime and public safety |
—
|
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: crime and public safety | Statement: [Willie Horton, issueFramedAs, crime and public safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueFramedAs Context triple: [Willie Horton, issueFramedAs, crime and public safety]
-
A.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
B.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
C.
framed
Indicates that one entity has been falsely presented or set up to appear responsible or guilty for an action or situation, typically to mislead others.
-
D.
issueIncludes
Indicates that an issue or problem encompasses, contains, or involves a specified element, component, or sub-issue as part of its scope.
-
E.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15858c13c819098fe66a50ecea7d7 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e73597b51c8190aeff27f4779b82f3 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 8:45 p.m.