Triple
T24502551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle in the Varbitsa Pass |
E617973
|
entity |
| Predicate | combatantLeaderTitle |
P2084
|
FINISHED |
| Object | Khan of Bulgaria |
—
|
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: Khan of Bulgaria | Statement: [Battle in the Varbitsa Pass, combatantLeaderTitle, Khan of Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantLeaderTitle Context triple: [Battle in the Varbitsa Pass, combatantLeaderTitle, Khan of Bulgaria]
-
A.
commanderTitle
chosen
Indicates the official rank or title held by the person who commands or leads a given entity.
-
B.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
C.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
D.
seniorEnlistedLeaderTitle
Indicates the formal title held by the senior enlisted leader in a military or similar hierarchical organization.
-
E.
politicalCommissarTitle
Indicates that an entity holds or is assigned the title or role of a political commissar within a political or military organization.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.