Triple
T702655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Approaches |
E14030
|
entity |
| Predicate | primaryFunctionDuringWWII |
P16542
|
FINISHED |
| Object | protection of merchant shipping |
—
|
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: protection of merchant shipping | Statement: [Western Approaches, primaryFunctionDuringWWII, protection of merchant shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionDuringWWII Context triple: [Western Approaches, primaryFunctionDuringWWII, protection of merchant shipping]
-
A.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
-
B.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
C.
WWIIUse
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
-
D.
preWorldWarIIRole
Indicates the role, position, or function an entity held or performed prior to the onset of World War II.
-
E.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.