Triple
T26273920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish naval campaign of 1677 |
E660505
|
entity |
| Predicate | opposingNavalForce |
P72629
|
FINISHED |
| Object | Swedish Navy |
—
|
NE NERFINISHED |
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: Swedish Navy | Statement: [Danish naval campaign of 1677, opposingNavalForce, Swedish Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingNavalForce Context triple: [Danish naval campaign of 1677, opposingNavalForce, Swedish Navy]
-
A.
navalOpposition
chosen
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
B.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
C.
opponentFleet
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
-
D.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
E.
navalForceTargeted
Indicates that a naval force is selected or designated as the target of an action or operation.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 9:53 p.m.