Triple
T21725487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Seville |
E536263
|
entity |
| Predicate | titleStyleLanguage |
P38219
|
FINISHED |
| Object | Spanish language |
—
|
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: Spanish language | Statement: [King of Seville, titleStyleLanguage, Spanish language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleStyleLanguage Context triple: [King of Seville, titleStyleLanguage, Spanish language]
-
A.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
-
B.
titleLanguageForm
chosen
Indicates the specific linguistic form or variant in which a title is expressed (e.g., language, script, or transliteration form).
-
C.
titleStyleAdopted
Indicates that a particular style or format for a title has been chosen and put into use for an entity.
-
D.
titlesStyle
Indicates the stylistic convention or formatting applied to titles in a given context or resource.
-
E.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another 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_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. |
Created at: April 16, 2026, 6:48 p.m.