Triple
T2194164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale West Campus research facilities |
E49932
|
entity |
| Predicate | supportsResearchIn |
P36686
|
FINISHED |
| Object | life 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: life sciences | Statement: [Yale West Campus research facilities, supportsResearchIn, life sciences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsResearchIn Context triple: [Yale West Campus research facilities, supportsResearchIn, life sciences]
-
A.
supportedResearch
Indicates that one entity provided assistance, resources, or backing to enable or advance the research activities of another entity.
-
B.
researchSupportType
Indicates the specific kind of support provided for research activities, such as funding, resources, or services.
-
C.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
D.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
E.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
- F. None of above. chosen
Provenance (4 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbea8bd4881908f72019a5acf6174 |
completed | March 7, 2026, 5:59 a.m. |
Created at: March 4, 2026, 7:46 p.m.