Triple
T24575258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of the German battleship Scharnhorst |
E608085
|
entity |
| Predicate | relatedConvoy |
P37
|
FINISHED |
| Object | JW 55B |
—
|
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: JW 55B | Statement: [sinking of the German battleship Scharnhorst, relatedConvoy, JW 55B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedConvoy Context triple: [sinking of the German battleship Scharnhorst, relatedConvoy, JW 55B]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
relatedVehicle
Indicates that there exists an associated or connected vehicle that has a relevant relationship to the primary entity.
-
C.
relatedExpedition
Indicates that one expedition has a connection or association with another expedition, such as being part of the same project, time period, or thematic context.
-
D.
relatedMission
Indicates that one mission is connected or associated with another mission in a meaningful way, such as by shared goals, context, participants, or timeline.
-
E.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a928896c8190af385755b1418ba6 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.