Triple
T28526537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Charles III of England and Scotland (Jacobite claim) |
E721921
|
entity |
| Predicate | claimedTitleStart |
P171461
|
FINISHED |
| Object | 1766 |
—
|
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: 1766 | Statement: [King Charles III of England and Scotland (Jacobite claim), claimedTitleStart, 1766]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedTitleStart Context triple: [King Charles III of England and Scotland (Jacobite claim), claimedTitleStart, 1766]
-
A.
claimedTitle
Indicates that an entity asserts or declares possession of a particular title or rank.
-
B.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
C.
titleClaimOutcome
Indicates the result or status of a claim to a title, such as whether the title was granted, denied, retained, or lost.
-
D.
titleContested
Indicates that the legitimacy or ownership of a title is disputed between parties.
-
E.
filedNativeTitleClaim
Indicates that an entity has formally lodged a legal claim asserting native or Indigenous title rights over a specific area of land or waters.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 28, 2026, 3:25 a.m.