Triple
T13700148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Utah |
E328493
|
entity |
| Predicate | assignment |
P65949
|
FINISHED |
| Object | investigate bank robberies by the Ex-Presidents |
—
|
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: investigate bank robberies by the Ex-Presidents | Statement: [Johnny Utah, assignment, investigate bank robberies by the Ex-Presidents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignment Context triple: [Johnny Utah, assignment, investigate bank robberies by the Ex-Presidents]
-
A.
assignmentType
Indicates the specific category or kind of assignment associated with an entity or activity.
-
B.
assignmentBasis
Indicates the criterion or rationale on which an assignment or allocation is determined.
-
C.
allocation
chosen
Indicates the distribution or assignment of resources, responsibilities, or items among entities according to some rule or plan.
-
D.
assessment
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
E.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc879adc88190b03f1cf815b71061 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.