Triple
T17262142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diskhaler |
E419032
|
entity |
| Predicate | administrationStep |
P126771
|
FINISHED |
| Object | load blister disc |
—
|
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: load blister disc | Statement: [Diskhaler, administrationStep, load blister disc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationStep Context triple: [Diskhaler, administrationStep, load blister disc]
-
A.
adminChange
Indicates that an administrative user performs or authorizes a modification to a system, resource, or configuration.
-
B.
enteredAdministration
Indicates that an entity has formally begun serving in an administrative role or office within an organization or institution.
-
C.
administrationRequired
Indicates that a particular action, process, or resource can only be performed, accessed, or modified when administrative authorization or privileges are present.
-
D.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
E.
adminStatus
Indicates that an entity holds an administrative role, privilege level, or state within a system or context.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e717a348190ae6835fb08f38125 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:39 a.m.