Triple
T8311130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaurians |
E194591
|
entity |
| Predicate | roleInIsaurianWar |
P67835
|
FINISHED |
| Object | rebels against Emperor Anastasius I |
—
|
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: rebels against Emperor Anastasius I | Statement: [Isaurians, roleInIsaurianWar, rebels against Emperor Anastasius I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInIsaurianWar Context triple: [Isaurians, roleInIsaurianWar, rebels against Emperor Anastasius I]
-
A.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
roleInGallicWars
Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
-
C.
strategicRoleDuringWar
chosen
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
D.
roleDuringConquest
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
E.
roleInWarsOfTheRoses
Indicates the specific part or function an entity played in the historical conflict known as the Wars of the Roses.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2eecb08190ae0ba8adbaf58c8f |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.