Triple
T24135053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Collecchio–Fornovo |
E598058
|
entity |
| Predicate | axisForcesStatus |
P154973
|
FINISHED |
| Object | retreating |
—
|
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: retreating | Statement: [Battle of Collecchio–Fornovo, axisForcesStatus, retreating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: axisForcesStatus Context triple: [Battle of Collecchio–Fornovo, axisForcesStatus, retreating]
-
A.
axisForces
Indicates a relationship where one entity exerts or applies force along, around, or with respect to a particular axis defined by another entity.
-
B.
axisForcesStrength
Indicates the magnitude or intensity of forces acting along a specified axis.
-
C.
axisForce
Indicates a force applied along a specific axis or direction between entities.
-
D.
inForceStatus
Indicates that a rule, agreement, or condition is currently active, valid, and legally or formally in effect.
-
E.
opposingForcesStatus
Indicates the current state or condition of two or more forces that are in conflict or opposition to each other.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7b6e9c819097fb546efa35821b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:26 p.m.