Triple
T31787947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Alexander Boswell, 1st Baronet |
E811381
|
entity |
| Predicate | reasonForDuel |
P191904
|
FINISHED |
| Object | political dispute |
—
|
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: political dispute | Statement: [Sir Alexander Boswell, 1st Baronet, reasonForDuel, political dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDuel Context triple: [Sir Alexander Boswell, 1st Baronet, reasonForDuel, political dispute]
-
A.
reasonForDuelingDisabled
Indicates that a specific reason or condition is preventing two parties from engaging in a duel.
-
B.
reasonForAttack
Indicates that one entity’s attack on another is motivated or caused by the specified reason.
-
C.
typeOfDuel
Indicates the specific kind or category of duel that characterizes a given dueling event or relationship between opponents.
-
D.
duelArrangedBy
Indicates that a duel between two parties has been set up, initiated, or formally organized by a specific agent or entity.
-
E.
causeOfVengeance
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: April 30, 2026, 11:38 p.m.