Triple
T23121810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Spercheios |
E576913
|
entity |
| Predicate | BulgarianCommander |
P136827
|
FINISHED |
| Object | Samuel 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: Samuel of Bulgaria | Statement: [Battle of Spercheios, BulgarianCommander, Samuel of Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BulgarianCommander Context triple: [Battle of Spercheios, BulgarianCommander, Samuel of Bulgaria]
-
A.
commanderForBulgaria
chosen
Indicates that an entity serves or has served in the role of commander on behalf of, or in the service of, Bulgaria.
-
B.
ByzantineCommander
Indicates a relationship where an entity holds the role or function of a commander within a Byzantine military or organizational context.
-
C.
ArmenianCommander
Indicates that an individual serves as a military commander associated with Armenia.
-
D.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
E.
ArgiveCommander
Indicates a relationship where an entity holds the role or status of a commander associated with Argos or the Argives.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e50c500819095d59aef44388153 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.