Triple
T28263374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beck Anxiety Inventory |
E712638
|
entity |
| Predicate | administrationMode |
P180502
|
FINISHED |
| Object | self-administered |
—
|
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: self-administered | Statement: [Beck Anxiety Inventory, administrationMode, self-administered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationMode Context triple: [Beck Anxiety Inventory, administrationMode, self-administered]
-
A.
adminStatus
Indicates that an entity holds an administrative role, privilege level, or state within a system or context.
-
B.
adminChange
Indicates that an administrative user performs or authorizes a modification to a system, resource, or configuration.
-
C.
administrationStep
Indicates a specific phase or stage within a broader administrative or management process.
-
D.
modeManaged
Indicates that one entity controls, configures, or oversees the operational mode or state of another entity.
-
E.
adminCenterType
Indicates the type or category of an entity that serves as an administrative center within a given jurisdiction or organization.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 27, 2026, 11:12 p.m.