Triple
T728451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Rothesay |
E14778
|
entity |
| Predicate | transferOnEvent |
P9014
|
FINISHED |
| Object | accession of holder to the throne |
—
|
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: accession of holder to the throne | Statement: [Duke of Rothesay, transferOnEvent, accession of holder to the throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferOnEvent Context triple: [Duke of Rothesay, transferOnEvent, accession of holder to the throne]
-
A.
functionTransferredTo
chosen
Indicates that a specific function, role, or responsibility has been moved from one entity to another.
-
B.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
conversionEvent
Indicates that a user or entity has completed a desired target action (such as a purchase, signup, or other goal) that counts as a successful conversion.
-
D.
migrationEvent
Indicates an event in which one or more entities move or relocate from one place or context to another, typically across defined boundaries or regions.
-
E.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f839608190878a60eb7a044ed9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.