Triple
T21234723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | François Hanriot |
E523312
|
entity |
| Predicate | wasExecutedOn |
P49637
|
FINISHED |
| Object | 1794-07-28 |
—
|
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: 1794-07-28 | Statement: [François Hanriot, wasExecutedOn, 1794-07-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasExecutedOn Context triple: [François Hanriot, wasExecutedOn, 1794-07-28]
-
A.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
B.
executedFor
Indicates that one entity carried out an action, task, or operation on behalf of or in fulfillment of an obligation to another entity.
-
C.
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.
-
D.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
E.
someMembersExecutedOn
Indicates that at least one member of a group was subjected to execution in relation to a specified event or context.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7351f0e988190bb77b598cb8a9532 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.