Triple
T1506968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huff-Duff |
E33922
|
entity |
| Predicate | helpedCounter |
P22516
|
FINISHED |
| Object | Battle of the Atlantic U-boat threat |
—
|
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: Battle of the Atlantic U-boat threat | Statement: [Huff-Duff, helpedCounter, Battle of the Atlantic U-boat threat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedCounter Context triple: [Huff-Duff, helpedCounter, Battle of the Atlantic U-boat threat]
-
A.
helpedLaunch
Indicates that one entity played a significant role in initiating, starting, or bringing another entity (such as a project, product, or organization) into operation or public release.
-
B.
helpedSecure
chosen
Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
-
C.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of another entity.
-
D.
hasHelpPoint
Indicates that one entity provides or contains a designated help or assistance point for another entity.
-
E.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.