Triple
T24070431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of Albert Snyder |
E596209
|
entity |
| Predicate | hasExecutionDateOfJuddGray |
P49637
|
FINISHED |
| Object | 1928-01-12 |
—
|
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: 1928-01-12 | Statement: [murder of Albert Snyder, hasExecutionDateOfJuddGray, 1928-01-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutionDateOfJuddGray Context triple: [murder of Albert Snyder, hasExecutionDateOfJuddGray, 1928-01-12]
-
A.
hasExecutionDate
chosen
Indicates that an entity is associated with a specific date on which an execution or carrying out of an action, order, or sentence is scheduled or took place.
-
B.
hasAllegedDate
Indicates that an entity is associated with a date that is claimed or reported, but not confirmed as certain.
-
C.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
D.
hasJudgeFrom
Indicates that an entity has a judge whose origin, affiliation, or source is from a specified place or organization.
-
E.
hasEcclesiasticalEvaluationDate
Indicates the date on which an official ecclesiastical (church) assessment or judgment regarding the subject was made.
- 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.