Triple
T5386824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asparuh of Bulgaria |
E120220
|
entity |
| Predicate | resultOfVictory |
P27457
|
FINISHED |
| Object | Byzantine recognition of the Bulgarian state |
—
|
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: Byzantine recognition of the Bulgarian state | Statement: [Asparuh of Bulgaria, resultOfVictory, Byzantine recognition of the Bulgarian state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfVictory Context triple: [Asparuh of Bulgaria, resultOfVictory, Byzantine recognition of the Bulgarian state]
-
A.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
B.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
C.
victoriousSide
Indicates which participant or group emerged as the winner in a competitive or conflict situation.
-
D.
strategicEffectOfVictory
chosen
Indicates that a victory produces a broader strategic impact or consequence beyond the immediate outcome of the conflict or contest.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f6f39c8190aa6af12370e3d12b |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.