Triple
T5176328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Helsingborg |
E116806
|
entity |
| Predicate | primaryObjectiveSweden |
P38163
|
FINISHED |
| Object | expel Danish forces from Scania |
—
|
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: expel Danish forces from Scania | Statement: [Battle of Helsingborg, primaryObjectiveSweden, expel Danish forces from Scania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryObjectiveSweden Context triple: [Battle of Helsingborg, primaryObjectiveSweden, expel Danish forces from Scania]
-
A.
primaryMissionTo
chosen
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
B.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
C.
strategicObjectiveSpain
Indicates that an entity has a strategic objective specifically related to Spain.
-
D.
PrussianObjective
Indicates that an entity has the goal, target, or strategic objective of achieving or advancing something specifically related to Prussia or Prussian interests.
-
E.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd797349008190b87ad9d0d3eb667f |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.