Triple
T6794960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Edgar Herold |
E156030
|
entity |
| Predicate | executedOn |
P49637
|
FINISHED |
| Object | 1865-07-07 |
—
|
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: 1865-07-07 | Statement: [David Edgar Herold, executedOn, 1865-07-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executedOn Context triple: [David Edgar Herold, executedOn, 1865-07-07]
-
A.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
B.
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.
-
C.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
D.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
E.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2c6e7dc8190b1f33372d047baba |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.