Triple
T25317756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIUK gap |
E634793
|
entity |
| Predicate | remainsImportantIn |
P1887
|
FINISHED |
| Object | 21st century naval strategy |
—
|
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: 21st century naval strategy | Statement: [GIUK gap, remainsImportantIn, 21st century naval strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsImportantIn Context triple: [GIUK gap, remainsImportantIn, 21st century naval strategy]
-
A.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
B.
remainedIn
Indicates that an entity stayed within or continued to be located in a particular place or state for a period of time.
-
C.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
D.
importantObject
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
-
E.
remainsLitDuring
Indicates that one entity continues to emit light or stay illuminated throughout the duration of another specified event or condition.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4968aece4819097e204da7b4e43cf |
completed | May 1, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:28 p.m.