Triple
T24856771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euphemia de Ross |
E622050
|
entity |
| Predicate | monarchConsortTitle |
P123691
|
FINISHED |
| Object | Queen consort of Scotland |
—
|
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: Queen consort of Scotland | Statement: [Euphemia de Ross, monarchConsortTitle, Queen consort of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchConsortTitle Context triple: [Euphemia de Ross, monarchConsortTitle, Queen consort of Scotland]
-
A.
monarchConsortOf
Indicates that one person is the spouse of a reigning monarch, holding the role of consort to that monarch.
-
B.
kingConsortOfTitle
Indicates that a male monarch holds the position of king consort corresponding to a specific noble or royal title.
-
C.
typeOfMonarchConsort
chosen
Indicates the specific kind or category of monarch’s spouse (consort) that an entity is, such as queen consort, prince consort, or empress consort.
-
D.
monarchOfConsort
Indicates that one entity is the consort (spouse) of the reigning monarch of another entity (typically a state or territory).
-
E.
consortTitleAtCoronation
Indicates the formal title held by a royal consort specifically at the time of a coronation.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.