Triple
T14694272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Derfflinger |
E345111
|
entity |
| Predicate | battleAchievement |
P32376
|
FINISHED |
| Object | helped sink HMS Queen Mary at Jutland |
—
|
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: helped sink HMS Queen Mary at Jutland | Statement: [SMS Derfflinger, battleAchievement, helped sink HMS Queen Mary at Jutland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleAchievement Context triple: [SMS Derfflinger, battleAchievement, helped sink HMS Queen Mary at Jutland]
-
A.
battleHonors
Indicates that an entity has been awarded or is associated with specific honors or distinctions earned through participation in battles or military engagements.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
battleDescribed
Indicates that a particular battle is described, depicted, or recounted in the referenced source or representation.
-
D.
combatRecord
chosen
Indicates that an entity maintains a documented history of its participation in combat or battles.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb586e7108190be644db9cf9a4d99 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.