Triple
T687845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeremy Thorpe |
E13322
|
entity |
| Predicate | notableAllegation |
P22
|
FINISHED |
| Object | conspiracy to murder Norman Scott |
—
|
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: conspiracy to murder Norman Scott | Statement: [Jeremy Thorpe, notableAllegation, conspiracy to murder Norman Scott]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAllegation Context triple: [Jeremy Thorpe, notableAllegation, conspiracy to murder Norman Scott]
-
A.
hasNotableClaim
Indicates that an entity is associated with a significant, widely recognized statement, assertion, or claim.
-
B.
notableProsecutor
Indicates that the person served as a prosecutor in a way that is widely recognized as significant or noteworthy.
-
C.
notableAdversary
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
-
D.
notableResolution
Indicates that an entity is distinguished or recognized for having a particularly important, impactful, or well-known resolution or decision.
-
E.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.