Triple
T30874335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Scutari |
E786432
|
entity |
| Predicate | opponentRemovedFromPower |
P81842
|
FINISHED |
| Object | Licinius I |
—
|
NE NERFINISHED |
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: Licinius I | Statement: [Battle of Scutari, opponentRemovedFromPower, Licinius I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentRemovedFromPower Context triple: [Battle of Scutari, opponentRemovedFromPower, Licinius I]
-
A.
wasRemovedFromPowerBy
chosen
Indicates that an entity lost its position of authority or control as a result of actions taken by another entity.
-
B.
opponentActionEnded
Indicates that an opposing party’s action or move has been completed or has come to an end.
-
C.
removedPower
Indicates that one entity has taken away or disabled the power, authority, or capability previously held by another entity.
-
D.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:48 p.m.