Triple
T16152822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar of Bulgaria |
E391956
|
entity |
| Predicate | usedHonorifically |
P119748
|
FINISHED |
| Object | title Tsar in medieval Bulgaria |
—
|
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: title Tsar in medieval Bulgaria | Statement: [Tsar of Bulgaria, usedHonorifically, title Tsar in medieval Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHonorifically Context triple: [Tsar of Bulgaria, usedHonorifically, title Tsar in medieval Bulgaria]
-
A.
honorificUse
chosen
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
C.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
D.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
E.
honorificConnotation
Indicates that one entity refers to or characterizes another using an honorific or respectful form, conveying deference or elevated social status.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d98d08c8190a15d4aee40d47220 |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.