Triple
T24070498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Howard |
E596211
|
entity |
| Predicate | capturedImageEvent |
P64243
|
FINISHED |
| Object | execution of Ruth Snyder |
—
|
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: execution of Ruth Snyder | Statement: [Tom Howard, capturedImageEvent, execution of Ruth Snyder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedImageEvent Context triple: [Tom Howard, capturedImageEvent, execution of Ruth Snyder]
-
A.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
C.
eventTypeCaptured
Indicates that the specific type or category of an event has been successfully recorded or logged.
-
D.
capturedUsing
chosen
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db17c99881909f97e858fb183d86 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.