Triple
T24070484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Judd Gray |
E596210
|
entity |
| Predicate | executionCarriedOutBy |
P46588
|
FINISHED |
| Object | State of New York |
—
|
NE NERFINISHED |
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: State of New York | Statement: [Henry Judd Gray, executionCarriedOutBy, State of New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionCarriedOutBy Context triple: [Henry Judd Gray, executionCarriedOutBy, State of New York]
-
A.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
B.
resolutionCarriedOutBy
Indicates that the execution or implementation of a resolution is performed by a specified agent or entity.
-
C.
executioner
chosen
Indicates that one entity performs or is responsible for carrying out an execution on another entity.
-
D.
executionerOrganization
Indicates that an organization is responsible for carrying out or executing a particular action, decision, or process on behalf of another party.
-
E.
isConductedBy
Indicates that an event, activity, or process is carried out, organized, or overseen by a particular agent or 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.