Triple
T12637234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaloyan of Bulgaria |
E301795
|
entity |
| Predicate | receivedCrownFrom |
P24696
|
FINISHED |
| Object | papal legate |
—
|
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: papal legate | Statement: [Kaloyan of Bulgaria, receivedCrownFrom, papal legate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedCrownFrom Context triple: [Kaloyan of Bulgaria, receivedCrownFrom, papal legate]
-
A.
crownPresent
Indicates that a crown is currently present on or with the relevant entity.
-
B.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
-
C.
crownedBy
chosen
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
-
D.
hasCrownCount
Indicates the number of crowns that an entity possesses or is associated with.
-
E.
crownedAt
Indicates the place or event where an entity formally received a crown or was officially installed as a monarch or titleholder.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.