Triple
T38538295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barracuda programme |
E924757
|
entity |
| Predicate | navalDomain |
P51623
|
FINISHED |
| Object | undersea warfare |
—
|
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: undersea warfare | Statement: [Barracuda programme, navalDomain, undersea warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalDomain Context triple: [Barracuda programme, navalDomain, undersea warfare]
-
A.
maritimeDomain
chosen
Indicates a relationship or activity that occurs within, affects, or is specifically associated with the maritime domain (seas, oceans, and related maritime operations).
-
B.
navalOperations
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
C.
navalDiscipline
Indicates the enforcement or maintenance of rules, order, and conduct within a naval or maritime context.
-
D.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
E.
navalCommand
Indicates a relationship where one entity holds authority to direct, control, or oversee naval forces or maritime military operations involving 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2e7f334819094f21b6af81b5e20 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.