Triple
T11194952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziyad ibn Salih |
E264897
|
entity |
| Predicate | resultOfCommandAtBattleOfTalas |
P19109
|
FINISHED |
| Object | Muslim victory |
—
|
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: Muslim victory | Statement: [Ziyad ibn Salih, resultOfCommandAtBattleOfTalas, Muslim victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfCommandAtBattleOfTalas Context triple: [Ziyad ibn Salih, resultOfCommandAtBattleOfTalas, Muslim victory]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
AbbasidCommander
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
C.
outcomeForOttomans
Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
-
D.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
-
E.
commanderSeljuk
Indicates that one entity served as a military commander within the Seljuk context (e.g., army, campaign, or polity) for the other 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.