Triple
T5448358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giovanni Marchese di Provera |
E122305
|
entity |
| Predicate | sideInBattleOfRivoli |
P64369
|
FINISHED |
| Object | Austrian side |
—
|
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: Austrian side | Statement: [Giovanni Marchese di Provera, sideInBattleOfRivoli, Austrian side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInBattleOfRivoli Context triple: [Giovanni Marchese di Provera, sideInBattleOfRivoli, Austrian side]
-
A.
opponentAtBattleOfTheNile
Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
-
B.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
-
C.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
D.
royalistForcesIncluded
Indicates that the composition of the royalist forces included the specified entity or group.
-
E.
mainOpponentOfAustria
Indicates that one entity is the primary rival or adversary of Austria in a given context (such as politics, war, or competition).
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd95bd53f48190a03144beb290f2cb |
completed | March 20, 2026, 6:45 p.m. |
Created at: March 20, 2026, 2:07 p.m.