Triple
T20289589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maloyaroslavets |
E509982
|
entity |
| Predicate | strategicRoleIn1812 |
P67835
|
FINISHED |
| Object | turning point of French retreat from Moscow |
—
|
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: turning point of French retreat from Moscow | Statement: [Maloyaroslavets, strategicRoleIn1812, turning point of French retreat from Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicRoleIn1812 Context triple: [Maloyaroslavets, strategicRoleIn1812, turning point of French retreat from Moscow]
-
A.
positionOnWarOf1812
Indicates a stance, opinion, or alignment that an entity holds regarding the War of 1812.
-
B.
strategicRoleDuringWar
chosen
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
C.
reasonForOppositionToWarOf1812
Indicates the specific rationale or grounds an entity has for opposing the War of 1812.
-
D.
strategicRoleIn
Indicates that one entity serves a strategic function, position, or importance within the context, operations, or objectives of another entity.
-
E.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67694d50881909d59c1037295c1d0 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:11 a.m.