Triple
T22149589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W80 warhead |
E547377
|
entity |
| Predicate | associatedNavalForce |
P23973
|
FINISHED |
| Object | U.S. attack submarines (for TLAM-N) |
—
|
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: U.S. attack submarines (for TLAM-N) | Statement: [W80 warhead, associatedNavalForce, U.S. attack submarines (for TLAM-N)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedNavalForce Context triple: [W80 warhead, associatedNavalForce, U.S. attack submarines (for TLAM-N)]
-
A.
navalForceInvolved
chosen
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
B.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
C.
countryNavalForce
Indicates that a country possesses, controls, or is associated with a particular naval military force.
-
D.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
E.
navalForceComposition
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f2c0e881909c3488bb5eb5959d |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.