Triple
T22702584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio V Alaudae |
E561360
|
entity |
| Predicate | loyaltyShiftedTo |
P91356
|
FINISHED |
| Object | Octavian after Actium |
—
|
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: Octavian after Actium | Statement: [Legio V Alaudae, loyaltyShiftedTo, Octavian after Actium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyShiftedTo Context triple: [Legio V Alaudae, loyaltyShiftedTo, Octavian after Actium]
-
A.
loyaltyChange
chosen
Indicates a change in the degree or direction of loyalty from one entity toward another over time.
-
B.
loyaltyRevealedIn
Indicates that an entity’s loyalty becomes evident or is demonstrated through a particular situation, action, or context.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyArc
Indicates a character’s progression in loyalty toward another entity, typically showing how trust, allegiance, or faithfulness strengthens, weakens, or transforms over time.
-
E.
isLoyalTo
Indicates that one entity consistently supports, respects, or remains faithful to another 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cbf5788190bc8cd1bc71a861e5 |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:16 p.m.