Triple
T24979575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Consort of the United Kingdom |
E625126
|
entity |
| Predicate | currentMonarchSpouseOf |
P88104
|
FINISHED |
| Object | King Charles III |
—
|
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: King Charles III | Statement: [Queen Consort of the United Kingdom, currentMonarchSpouseOf, King Charles III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMonarchSpouseOf Context triple: [Queen Consort of the United Kingdom, currentMonarchSpouseOf, King Charles III]
-
A.
spouseIsMonarchOf
chosen
Indicates that a person's spouse holds the position of monarch (ruler) of a specified country or territory.
-
B.
regentSpouse
Indicates that one person is the spouse of a regent, i.e., married to an individual who rules on behalf of a monarch or in place of the sovereign.
-
C.
spouseServedMonarch
Indicates that the spouse of a person held a position of service or duty to a monarch.
-
D.
marriedToMonarchFrom
Indicates that a person is married to a monarch who rules or comes from a specified country or region.
-
E.
spouseOfHeirToThrone
Indicates that one person is the married partner of an individual who is the heir to a throne.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:02 a.m.