Triple
T28398568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Bridge |
E719343
|
entity |
| Predicate | RashidunCavalryComponent |
P164704
|
FINISHED |
| Object | Arab cavalry |
—
|
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: Arab cavalry | Statement: [Battle of the Bridge, RashidunCavalryComponent, Arab cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RashidunCavalryComponent Context triple: [Battle of the Bridge, RashidunCavalryComponent, Arab cavalry]
-
A.
AbbasidCommander
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
B.
ArabCommander
Indicates that the subject serves as a military commander associated with Arab forces or entities.
-
C.
RashidunForcesStrength
Indicates the size or numerical strength of the Rashidun forces involved in a particular military context or engagement.
-
D.
hasCavalryHeritage
Indicates that an entity has a historical or traditional connection to cavalry forces or mounted military service.
-
E.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:18 a.m.