Triple
T7049201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slag bij Lowestoft |
E163721
|
entity |
| Predicate | combatant2Strength |
P1404
|
FINISHED |
| Object | Dutch fleet |
—
|
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: Dutch fleet | Statement: [Slag bij Lowestoft, combatant2Strength, Dutch fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatant2Strength Context triple: [Slag bij Lowestoft, combatant2Strength, Dutch fleet]
-
A.
combatantStrength
chosen
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
B.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
C.
attackerStrength
Indicates the level or magnitude of power, force, or capability possessed by the attacking entity in a given interaction or scenario.
-
D.
opponentForceCharacteristic
Indicates a characteristic or attribute that describes the nature, capability, or condition of an opposing force.
-
E.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.