Triple
T960074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince William Augustus, Duke of Cumberland |
E20713
|
entity |
| Predicate | causeOfNickname |
P7596
|
FINISHED |
| Object | harsh repression after the Battle of Culloden |
—
|
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: harsh repression after the Battle of Culloden | Statement: [Prince William Augustus, Duke of Cumberland, causeOfNickname, harsh repression after the Battle of Culloden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfNickname Context triple: [Prince William Augustus, Duke of Cumberland, causeOfNickname, harsh repression after the Battle of Culloden]
-
A.
reasonForNickname
chosen
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
C.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
D.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
-
E.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b412f9f48190be123e8c20f38962 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.