Triple
T7197531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tali–Ihantala |
E168652
|
entity |
| Predicate | objectiveFinnish |
P64674
|
FINISHED |
| Object | halt Soviet offensive |
—
|
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: halt Soviet offensive | Statement: [Battle of Tali–Ihantala, objectiveFinnish, halt Soviet offensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveFinnish Context triple: [Battle of Tali–Ihantala, objectiveFinnish, halt Soviet offensive]
-
A.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
B.
polishObjective
Indicates that an entity’s goal or target is to improve, refine, or perfect another entity.
-
C.
objectiveIncludes
Indicates that a broader objective encompasses or contains a specific sub-objective, component, or element as part of its scope.
-
D.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
E.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92a5d288190955f703470e75bf3 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:51 p.m.