Triple
T25743323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSBN(X) program |
E648276
|
entity |
| Predicate | plannedFleetRole |
P21890
|
FINISHED |
| Object | continuous at-sea deterrent patrols |
—
|
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: continuous at-sea deterrent patrols | Statement: [SSBN(X) program, plannedFleetRole, continuous at-sea deterrent patrols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFleetRole Context triple: [SSBN(X) program, plannedFleetRole, continuous at-sea deterrent patrols]
-
A.
plannedRole
chosen
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
B.
propulsionRole
Indicates the specific function or responsibility an entity has within a propulsion system or propulsion-related process.
-
C.
targetFleetType
Indicates the specific category or classification of fleet that is the intended focus or recipient of an action or relationship.
-
D.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
-
E.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 3:47 a.m.