Triple
T34952153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Majesty the King of Bohemia |
E1008028
|
entity |
| Predicate | correspondsToTitleInLatin |
P37756
|
FINISHED |
| Object | Rex Bohemiae |
—
|
NE NERFINISHED |
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: Rex Bohemiae | Statement: [His Majesty the King of Bohemia, correspondsToTitleInLatin, Rex Bohemiae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToTitleInLatin Context triple: [His Majesty the King of Bohemia, correspondsToTitleInLatin, Rex Bohemiae]
-
A.
hasLatinTitleOf
chosen
Indicates that one entity has, uses, or is associated with the Latin-language title corresponding to another entity.
-
B.
hasLatinTitle
Indicates that an entity possesses a title or name expressed in Latin.
-
C.
hasTitleInEnglishOrthography
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
D.
titleInLatinScript
Indicates that the title of an entity is written or represented using a Latin-based writing system.
-
E.
hasTitleInTransliteration
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.