Triple
T36539346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etaples mutiny |
E900673
|
entity |
| Predicate | executedPerson |
P78073
|
FINISHED |
| Object | Private Arthur John (or James) McColl |
—
|
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: Private Arthur John (or James) McColl | Statement: [Etaples mutiny, executedPerson, Private Arthur John (or James) McColl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executedPerson Context triple: [Etaples mutiny, executedPerson, Private Arthur John (or James) McColl]
-
A.
executioner
Indicates that one entity performs or is responsible for carrying out an execution on another entity.
-
B.
executionerOrganization
Indicates that an organization is responsible for carrying out or executing a particular action, decision, or process on behalf of another party.
-
C.
subjectOfExecution
chosen
Indicates that one entity is the object or target upon which an execution (carrying out of a death sentence) is performed by another entity.
-
D.
executionMethodForPerpetrator
Indicates the method or means by which a perpetrator carried out an execution.
-
E.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.