Triple
T2827261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth de Burgh, Queen of Scots |
E54953
|
entity |
| Predicate | spouseTitleDuringMarriage |
P21956
|
FINISHED |
| Object | King of Scots |
—
|
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: King of Scots | Statement: [Elizabeth de Burgh, Queen of Scots, spouseTitleDuringMarriage, King of Scots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseTitleDuringMarriage Context triple: [Elizabeth de Burgh, Queen of Scots, spouseTitleDuringMarriage, King of Scots]
-
A.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
B.
currentTitleHolderSpouseOf
Indicates that one entity is the current spouse of the individual who presently holds a specified title.
-
C.
marriageThroughWhichTitleHeld
chosen
Indicates that a noble or formal title is held by a person specifically by virtue of (i.e., as a result of) a particular marriage.
-
D.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
E.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde95d8148190bcae8b0659a5c116 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.