Triple
T15015966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio-class ballistic missile submarine |
E377959
|
entity |
| Predicate | patrolType |
P116371
|
FINISHED |
| Object | deterrent patrol |
—
|
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: deterrent patrol | Statement: [Ohio-class ballistic missile submarine, patrolType, deterrent patrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patrolType Context triple: [Ohio-class ballistic missile submarine, patrolType, deterrent patrol]
-
A.
patrolledBy
Indicates that an area, route, or domain is regularly monitored or guarded by a specific agent or group.
-
B.
policeUnit
Indicates that one entity is a police unit (such as a department, squad, or division) associated with or responsible for another entity.
-
C.
policeDepartmentType
Indicates the specific organizational category or classification of a police department (e.g., municipal, state, federal).
-
D.
coastGuardType
Indicates that one entity is classified as a specific type or category within a coast guard organization.
-
E.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
- F. None of above. chosen
Provenance (4 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7623c3c819092ca36b358b01842 |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.