Triple
T31439942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USPHS cap device |
E802037
|
entity |
| Predicate | useRestrictedTo |
P8521
|
FINISHED |
| Object | authorized USPHS personnel |
—
|
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: authorized USPHS personnel | Statement: [USPHS cap device, useRestrictedTo, authorized USPHS personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useRestrictedTo Context triple: [USPHS cap device, useRestrictedTo, authorized USPHS personnel]
-
A.
accessRestrictedTo
chosen
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
B.
oftenRestrictedTo
Indicates that the use, occurrence, or applicability of something is frequently limited to a particular subset, context, or condition.
-
C.
productionRestrictedTo
Indicates that the production or manufacture of something is limited or confined to a specified location, entity, or set of conditions.
-
D.
nameUseRestrictedTo
Indicates that the use of a particular name is limited or confined to a specified context, scope, or set of conditions.
-
E.
accessRestrictedSince
Indicates that access to an entity has been limited or blocked starting from a specified point in time.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:04 p.m.