Triple
T22029534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDRs |
E544048
|
entity |
| Predicate | lessFrequentFor |
P19183
|
FINISHED |
| Object | conditions not expected to improve |
—
|
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: conditions not expected to improve | Statement: [CDRs, lessFrequentFor, conditions not expected to improve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessFrequentFor Context triple: [CDRs, lessFrequentFor, conditions not expected to improve]
-
A.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
B.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
C.
usedLessIn
Indicates that one entity is used with a lower frequency or intensity compared to another entity.
-
D.
lessOptimizedFor
Indicates that one entity is designed, configured, or adapted to perform a task or function with lower efficiency or effectiveness compared to another entity.
-
E.
isLessCommonThan
chosen
Indicates that one item occurs, appears, or is observed less frequently than another item.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ebf6d48190b84e7a45bbf9049c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.