Triple
T16103400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HRT |
E390678
|
entity |
| Predicate | typicalPatientGroup |
P35131
|
FINISHED |
| Object | perimenopausal women |
—
|
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: perimenopausal women | Statement: [HRT, typicalPatientGroup, perimenopausal women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPatientGroup Context triple: [HRT, typicalPatientGroup, perimenopausal women]
-
A.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
B.
hasPatientGroup
chosen
Indicates a relationship in which an entity (such as a study, treatment, or clinical activity) is associated with a specific group of patients it involves or targets.
-
C.
primaryPatientType
Indicates the main category or classification of patient that is primarily associated with or targeted by an entity, action, or service.
-
D.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
E.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6a4b8881908e8dc186381196d8 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.