Triple
T28263299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beck Depression Inventory |
E712637
|
entity |
| Predicate | timeFrameAssessed |
P58040
|
FINISHED |
| Object | past two weeks |
—
|
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: past two weeks | Statement: [Beck Depression Inventory, timeFrameAssessed, past two weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFrameAssessed Context triple: [Beck Depression Inventory, timeFrameAssessed, past two weeks]
-
A.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
B.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
C.
timePeriodAnalyzed
chosen
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6441b33e0819081dc4b8b5a12644f |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:12 p.m.