Triple
T26031840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Scott, 1st Duke of Monmouth |
E647449
|
entity |
| Predicate | executionerAuthority |
P160964
|
FINISHED |
| Object | English Crown |
—
|
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: English Crown | Statement: [James Scott, 1st Duke of Monmouth, executionerAuthority, English Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionerAuthority Context triple: [James Scott, 1st Duke of Monmouth, executionerAuthority, English Crown]
-
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.
executionerState
Indicates the current status or condition of an entity acting as an executioner within a given process or context.
-
D.
victimOfExecutionBy
Indicates that one entity was executed as a result of an execution carried out by another entity.
-
E.
placeOfExecution
Indicates the location where an execution or carrying out of a sentence, order, or legal punishment took place.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60dfaeebc8190ac01d3a0030acf55 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c68b02c8190870758d79cdec68b |
completed | May 2, 2026, 2:38 p.m. |
Created at: April 22, 2026, 9:06 a.m.