Triple
T21080211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tollund Man |
E519343
|
entity |
| Predicate | evidenceOfExecution |
P135517
|
FINISHED |
| Object | noose around neck |
—
|
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: noose around neck | Statement: [Tollund Man, evidenceOfExecution, noose around neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceOfExecution Context triple: [Tollund Man, evidenceOfExecution, noose around neck]
-
A.
executedFor
Indicates that one entity carried out an action, task, or operation on behalf of or in fulfillment of an obligation to another entity.
-
B.
hasProcessEvidence
chosen
Indicates that there is supporting evidence for a process or procedure associated with the subject in relation to the object.
-
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.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
E.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702da7be881908e430518103d7bb1 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.