Triple
T26220549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proclamation of Accession |
E655752
|
entity |
| Predicate | doesNotCreate |
P162142
|
FINISHED |
| Object | kingship |
—
|
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: kingship | Statement: [Proclamation of Accession, doesNotCreate, kingship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotCreate Context triple: [Proclamation of Accession, doesNotCreate, kingship]
-
A.
doesNotReplace
Indicates that one entity does not take over, substitute for, or serve as a replacement for another entity in a given context.
-
B.
doesNotCommitTo
Indicates that one entity refrains from making a promise, obligation, or firm decision toward another entity or course of action.
-
C.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
D.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
E.
doesNotTry
Indicates that an entity makes no attempt to perform a particular action or engage in a specified activity.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 26, 2026, 8:55 p.m.