Triple
T33111395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German High Seas Fleet |
E847340
|
entity |
| Predicate | tacticsAfterJutland |
P30685
|
FINISHED |
| Object | limited sorties into the North Sea |
—
|
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: limited sorties into the North Sea | Statement: [German High Seas Fleet, tacticsAfterJutland, limited sorties into the North Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsAfterJutland Context triple: [German High Seas Fleet, tacticsAfterJutland, limited sorties into the North Sea]
-
A.
enemyEngagementAtJutland
Indicates that an entity participated in or was involved in hostile military action against an enemy during the Battle of Jutland.
-
B.
navalTacticsImpact
Indicates how naval tactics influence the outcome, effectiveness, or dynamics of a maritime operation or engagement.
-
C.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
D.
survivorsAtJutland
Indicates that the entities were survivors of the Battle of Jutland.
-
E.
tacticOf
Indicates that one entity is a tactic, method, or strategy employed or used by another entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6eb33648190b26122f53c88d8eb |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.