Triple
T33974901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RHINE |
E871107
|
entity |
| Predicate | hasExperimentalArm |
P21872
|
FINISHED |
| Object | faricimab fixed dosing |
—
|
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: faricimab fixed dosing | Statement: [RHINE, hasExperimentalArm, faricimab fixed dosing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExperimentalArm Context triple: [RHINE, hasExperimentalArm, faricimab fixed dosing]
-
A.
hasExperimentalProduction
Indicates that an entity is involved in or associated with a production process that is experimental or in a trial phase rather than standard or fully established.
-
B.
hasArm
chosen
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
C.
supportsARMv8_5A
Indicates that the subject provides compatibility with, or implements the features of, the ARMv8.5-A architecture.
-
D.
isExperimental
Indicates that the subject is in an experimental or trial phase, not yet finalized or established as standard.
-
E.
supportsARMv8CryptographyExtensions
Indicates that the subject provides or is compatible with the ARMv8 cryptographic instruction set extensions for hardware-accelerated encryption and related operations.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:50 a.m.