Triple
T22482088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Callinicum |
E555790
|
entity |
| Predicate | SasanianAllies |
P98884
|
FINISHED |
| Object | Lakhmid Arab allies |
—
|
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: Lakhmid Arab allies | Statement: [Battle of Callinicum, SasanianAllies, Lakhmid Arab allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SasanianAllies Context triple: [Battle of Callinicum, SasanianAllies, Lakhmid Arab allies]
-
A.
sideSasanian
chosen
Indicates that an entity is aligned with, belongs to, or is on the side of the Sasanian faction or polity in a given context.
-
B.
PersianDynasty
Indicates a dynastic relationship in which a ruling house or lineage belongs to, originates from, or is associated with Persia or the Persian cultural-political sphere.
-
C.
ParthianForceType
Indicates the type or classification of a military force associated with the Parthians.
-
D.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
-
E.
نوقشفي
Indicates that something or someone was discussed or debated within a particular context or setting.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3a3b688190b41599979d038d85 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.