Triple
T10821825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Scotland |
E255387
|
entity |
| Predicate | typeOfMonarchyRole |
P25666
|
FINISHED |
| Object | hereditary by marriage |
—
|
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: hereditary by marriage | Statement: [Queen of Scotland, typeOfMonarchyRole, hereditary by marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonarchyRole Context triple: [Queen of Scotland, typeOfMonarchyRole, hereditary by marriage]
-
A.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
B.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
-
C.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
D.
symbolicRoleOfMonarch
Indicates that a monarch holds a primarily ceremonial or representational role rather than exercising substantive governing power.
-
E.
positionOnMonarchy
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344ae2688190bceabf41c79d298d |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.