Triple
T34981104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kriegsmarine U-boat wolfpack |
E1008815
|
entity |
| Predicate | peakEffectiveness |
P35920
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Kriegsmarine U-boat wolfpack, peakEffectiveness, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakEffectiveness Context triple: [Kriegsmarine U-boat wolfpack, peakEffectiveness, 1941]
-
A.
peakUse
chosen
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
B.
maximumEfficiency
Indicates that an entity operates at its highest possible level of performance or productivity under given conditions.
-
C.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
-
D.
peakContribution
Indicates the maximum level or amount that an entity contributes to another entity, process, or outcome within a given context.
-
E.
effectiveWithin
Indicates that one entity (such as a rule, condition, or effect) is valid, applicable, or in force only during a specified time period or within a defined contextual boundary.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.