Triple
T28919997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lazarus Man |
E733481
|
entity |
| Predicate | hasAttemptedExecution |
P166515
|
FINISHED |
| Object | protagonist targeted for hanging |
—
|
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: protagonist targeted for hanging | Statement: [The Lazarus Man, hasAttemptedExecution, protagonist targeted for hanging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttemptedExecution Context triple: [The Lazarus Man, hasAttemptedExecution, protagonist targeted for hanging]
-
A.
hasRun
Indicates that an entity has performed or completed a running activity or event at least once in the past.
-
B.
hasExecutionDate
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.
-
C.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
-
D.
wasTriedAfter
Indicates that one trial or legal proceeding occurred subsequent to another in time.
-
E.
isExecutedFor
Indicates that an action, plan, or process is carried out on behalf of, or in service of, a particular entity or purpose.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 8:18 a.m.