Triple
T16385940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ongal |
E397921
|
entity |
| Predicate | primaryBulgarLeaderTitle |
P123205
|
FINISHED |
| Object | khan |
—
|
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: khan | Statement: [Battle of Ongal, primaryBulgarLeaderTitle, khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBulgarLeaderTitle Context triple: [Battle of Ongal, primaryBulgarLeaderTitle, khan]
-
A.
officeHolderTitleInBulgarian
Indicates the official title or designation of an office holder as expressed in the Bulgarian language.
-
B.
founderOfDynastyInBulgaria
Indicates that a person is the founder or originator of a particular dynasty that ruled or existed in Bulgaria.
-
C.
commanderOfWallachia
Indicates that one entity serves as the military commander responsible for the forces or defense of Wallachia.
-
D.
nameInBulgarian
Indicates that an entity is referred to by a specific name when expressed in the Bulgarian language.
-
E.
MuscoviteLeader
Indicates a leadership relationship in which the subject serves as a leader or ruler of Muscovites or the Muscovite state.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263d260081909db9ac6016d5738a |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.