Triple
T11297920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offspring Cohort |
E267501
|
entity |
| Predicate | studyFocus |
P778
|
FINISHED |
| Object | cardiovascular disease |
—
|
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: cardiovascular disease | Statement: [Offspring Cohort, studyFocus, cardiovascular disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studyFocus Context triple: [Offspring Cohort, studyFocus, cardiovascular disease]
-
A.
studiesFor
Indicates that one entity engages in studying or academic preparation with the purpose of achieving or supporting another entity (such as a goal, exam, or qualification).
-
B.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
C.
academicFocus
chosen
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
D.
programFocus
Indicates that an educational or training program is primarily oriented around or concentrated on a particular subject, theme, or objective.
-
E.
studyMethods
Indicates that an entity uses or engages in particular methods or techniques for studying.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a3616c8190a8fd23ca67463806 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.