Triple
T22295019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German destroyer Z30 |
E551094
|
entity |
| Predicate | navalEngagementWith |
P72629
|
FINISHED |
| Object | Allied naval forces |
—
|
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: Allied naval forces | Statement: [German destroyer Z30, navalEngagementWith, Allied naval forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalEngagementWith Context triple: [German destroyer Z30, navalEngagementWith, Allied naval forces]
-
A.
navalEngagementType
Indicates the specific kind or category of naval combat or maritime military engagement involved in the relationship.
-
B.
navalOpposition
chosen
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
C.
navalVictoryOver
Indicates that one party has defeated another in a military engagement at sea.
-
D.
navalEngagementRole
Indicates the specific function or duty an entity performs within a naval engagement or maritime combat operation.
-
E.
includedNavalBattle
Indicates that one entity participated in or contained a specific naval battle as part of its events or composition.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560f06008190b58e71f7c1bd46f7 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.