Triple
T29042651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HHD |
E738039
|
entity |
| Predicate | academicDisciplineArea |
P778
|
FINISHED |
| Object | health sciences |
—
|
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: health sciences | Statement: [HHD, academicDisciplineArea, health sciences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicDisciplineArea Context triple: [HHD, academicDisciplineArea, health sciences]
-
A.
regionOfAcademicFocus
Indicates the academic subject area or discipline that an entity (such as a person or program) primarily concentrates on or specializes in.
-
B.
housesAcademicDiscipline
Indicates that an entity serves as the location or institutional home where a particular academic discipline is based, organized, or conducted.
-
C.
academicFocus
chosen
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
D.
regionOfAcademicInterest
Indicates that an entity has a particular academic field or subject area as its focus of interest or study.
-
E.
disciplinaryFocus
Indicates the primary academic or professional field, subject area, or discipline that something is centered on or concerned with.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 10:02 a.m.