Triple
T33988635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boehringer Ingelheim |
E871479
|
entity |
| Predicate | isResearchDriven |
P93061
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Boehringer Ingelheim, isResearchDriven, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResearchDriven Context triple: [Boehringer Ingelheim, isResearchDriven, true]
-
A.
isResearchOriented
chosen
Indicates that an entity is primarily focused on conducting, supporting, or advancing research activities.
-
B.
hasResearchComponent
Indicates that an entity includes, involves, or is associated with a research-related component or activity.
-
C.
motivatedResearchIn
Indicates that one entity inspired, drove, or provided the motivation for another entity to conduct a particular research activity or line of inquiry.
-
D.
researchValue
Indicates that something is considered useful, important, or relevant for research or scholarly investigation.
-
E.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7039045e88190b268522ba43a9cf5 |
completed | May 3, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f70101ba1c819099380274e6df9a4d |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.