Triple
T23622548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Security Guard detachment |
E583359
|
entity |
| Predicate | scopeOfDeployment |
P125950
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [Marine Security Guard detachment, scopeOfDeployment, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfDeployment Context triple: [Marine Security Guard detachment, scopeOfDeployment, worldwide]
-
A.
typeOfDeployment
Indicates the specific manner or configuration in which something (such as a system, application, or resource) is deployed or made operational.
-
B.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
C.
globalDeployment
chosen
Indicates that something is deployed, implemented, or made available across multiple countries or worldwide locations.
-
D.
installationScope
Indicates the extent or range within which an installation is applied, managed, or affects relevant entities.
-
E.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17ae58c8190b7b6cdc57c6ead3a |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.