Triple
T5176317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Helsingborg |
E116806
|
entity |
| Predicate | DanishArmyComposition |
P6154
|
FINISHED |
| Object | infantry, cavalry and artillery |
—
|
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: infantry, cavalry and artillery | Statement: [Battle of Helsingborg, DanishArmyComposition, infantry, cavalry and artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DanishArmyComposition Context triple: [Battle of Helsingborg, DanishArmyComposition, infantry, cavalry and artillery]
-
A.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
C.
alliedForcesComposition
Indicates the makeup and relative proportions of different military or paramilitary groups that are joined together as allied forces in a given context.
-
D.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
-
E.
orderOfBattleFeature
Indicates a specific structural or organizational characteristic associated with a military order of 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_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.