Triple
T21725494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Seville |
E536263
|
entity |
| Predicate | titleInMonarchFullStyle |
P145102
|
FINISHED |
| Object | subsidiary royal title |
—
|
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: subsidiary royal title | Statement: [King of Seville, titleInMonarchFullStyle, subsidiary royal title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInMonarchFullStyle Context triple: [King of Seville, titleInMonarchFullStyle, subsidiary royal title]
-
A.
styleOfMonarchTitle
Indicates the specific formal style or wording used in the official title of a monarch.
-
B.
monarchTitleIn
Indicates that a particular monarch holds or held a specific royal title within a given political or territorial entity.
-
C.
typeOfMonarchyTitle
Indicates that a given title is a specific type or category of monarchy-related title (e.g., king, queen, emperor) within a monarchical system.
-
D.
titleReign
Indicates the period during which a particular title was officially held or exercised by an entity.
-
E.
servedMonarchTitle
Indicates that one entity held a specific royal or noble title while serving as the reigning monarch over another entity.
- F. None of above. chosen
Provenance (4 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd972ed248190bd0d4ac43efccbfd |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:48 p.m.