Triple
T17354315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Pre-Clinical Innovation |
E421894
|
entity |
| Predicate | researchStage |
P127161
|
FINISHED |
| Object | early-stage |
—
|
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: early-stage | Statement: [Division of Pre-Clinical Innovation, researchStage, early-stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchStage Context triple: [Division of Pre-Clinical Innovation, researchStage, early-stage]
-
A.
researchMode
Indicates that an entity is engaged in or configured for conducting systematic investigation, experimentation, or study.
-
B.
researchBegan
Indicates that the activity of conducting research was initiated at a specific point in time.
-
C.
researchValue
Indicates that something is considered useful, important, or relevant for research or scholarly investigation.
-
D.
researchProjectAt
Indicates that a research project is conducted, hosted, or based at a particular institution or organization.
-
E.
researchComponent
Indicates that an entity functions as a part or element within a broader research activity, project, or study.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2f26548190a8822b2470ec3c72 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.