Triple
T28653135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Ceylon |
E725253
|
entity |
| Predicate | alsoMonarchOf |
P26694
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [King of Ceylon, alsoMonarchOf, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoMonarchOf Context triple: [King of Ceylon, alsoMonarchOf, United Kingdom]
-
A.
alsoKingOf
chosen
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
B.
monarchSheIsHeirTo
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
-
C.
confirmedMonarch
Indicates that an entity has been formally recognized and validated as the legitimate monarch, typically through an official confirmation process.
-
D.
electedMonarchOf
Indicates that one entity has been chosen through an election process to serve as the monarch (sovereign ruler) of another entity, typically a state or polity.
-
E.
representedMonarch
Indicates that one entity formally acted on behalf of, or served as the official representative of, a monarch in some capacity or context.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:53 a.m.