Triple
T1004680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Rivoli |
E21681
|
entity |
| Predicate | AustrianGunsCaptured |
P22215
|
FINISHED |
| Object | around 40 guns |
—
|
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: around 40 guns | Statement: [Battle of Rivoli, AustrianGunsCaptured, around 40 guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustrianGunsCaptured Context triple: [Battle of Rivoli, AustrianGunsCaptured, around 40 guns]
-
A.
FrenchImperialGunsLost
Indicates that French imperial forces lost their artillery or guns in a particular event or context.
-
B.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
C.
AustrianStrength
Indicates a relationship where an entity possesses or exhibits strength specifically associated with Austria, such as Austrian power, influence, or capability.
-
D.
RussoAustrianObjective
Indicates a shared objective or goal jointly pursued by Russian and Austrian parties or forces.
-
E.
AustrianObjective
Indicates that an entity has an objective, goal, or purpose specifically associated with Austria or Austrian context.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4ff614081909478500ada1f5059 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b1f4f88190822598cfd2a0fd2b |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.