Triple
T30697358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Marlborough |
E781510
|
entity |
| Predicate | statusAfterJutland |
P47778
|
FINISHED |
| Object | survived and returned to service |
—
|
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: survived and returned to service | Statement: [HMS Marlborough, statusAfterJutland, survived and returned to service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterJutland Context triple: [HMS Marlborough, statusAfterJutland, survived and returned to service]
-
A.
enemyEngagementAtJutland
Indicates that an entity participated in or was involved in hostile military action against an enemy during the Battle of Jutland.
-
B.
survivorsAtJutland
chosen
Indicates that the entities were survivors of the Battle of Jutland.
-
C.
battleOfJutlandDate
Indicates the specific calendar date on which the Battle of Jutland took place.
-
D.
statusOfTirpitzAfterOperation
Indicates the condition or state of the Tirpitz following the specified military operation.
-
E.
AustrianFleetOutcome
Indicates the result or consequence experienced by the Austrian fleet in a particular engagement or context.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 8:34 p.m.