Triple
T11074638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruxience |
E261831
|
entity |
| Predicate | hasRegulatoryType |
P14058
|
FINISHED |
| Object | biosimilar approval pathway |
—
|
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: biosimilar approval pathway | Statement: [Ruxience, hasRegulatoryType, biosimilar approval pathway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulatoryType Context triple: [Ruxience, hasRegulatoryType, biosimilar approval pathway]
-
A.
regulatoryType
chosen
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
B.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
C.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
D.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
-
E.
worksOnRegulationType
Indicates that an entity is involved in work or activities related to a specific type or category of regulation.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994efb608190a81bc8c4d16ddbd0 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.