Triple
T313563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBE |
E7656
|
entity |
| Predicate | orderSovereign |
P2801
|
FINISHED |
| Object | monarch of the United Kingdom |
—
|
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: monarch of the United Kingdom | Statement: [KBE, orderSovereign, monarch of the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderSovereign Context triple: [KBE, orderSovereign, monarch of the United Kingdom]
-
A.
sovereignComponent
Indicates that one entity functions as a constituent part of a larger sovereign whole, such as a state, polity, or authority.
-
B.
sovereignState
Indicates that an entity is recognized as an independent, self-governing state with ultimate authority over its territory and not subject to any higher political power.
-
C.
appliesToSovereignState
Indicates that something (such as a rule, status, or attribute) is applicable to, or in effect for, a sovereign state.
-
D.
formerSovereign
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
-
E.
orderFoundedBy
chosen
Indicates that a particular order or organization was established or created by a specific person or entity.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.