Triple
T19772708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospira |
E474927
|
entity |
| Predicate | notableBiosimilarArea |
P137272
|
FINISHED |
| Object | oncology |
—
|
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: oncology | Statement: [Hospira, notableBiosimilarArea, oncology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBiosimilarArea Context triple: [Hospira, notableBiosimilarArea, oncology]
-
A.
notableOperationArea
Indicates the geographic area or region where an entity primarily conducts or is recognized for its significant operations or activities.
-
B.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
C.
notableTargetArea
Indicates that an action, effect, or focus is specifically directed toward a particularly important or prominent area or region.
-
D.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
E.
notableGrowingArea
Indicates that a location is recognized as an important or prominent area for cultivating or producing a particular crop or product.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535ce4d08190a1dfca2df95a8631 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.