Triple
T33974900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RHINE |
E871107
|
entity |
| Predicate | hasControlArm |
P21872
|
FINISHED |
| Object | aflibercept 2 mg every 8 weeks after loading |
—
|
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: aflibercept 2 mg every 8 weeks after loading | Statement: [RHINE, hasControlArm, aflibercept 2 mg every 8 weeks after loading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlArm Context triple: [RHINE, hasControlArm, aflibercept 2 mg every 8 weeks after loading]
-
A.
hasArm
chosen
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
B.
hasArmConfiguration
Indicates that an entity is associated with a specific arrangement or setup of its arms or arm-like components.
-
C.
armsControl
Indicates a relationship where parties engage in limiting, regulating, or reducing weapons and military capabilities, often through agreements or treaties.
-
D.
hasArmCount
Indicates the number of arms that an entity possesses.
-
E.
armsControlStatus
Indicates the current state or condition of agreements, measures, or activities related to the limitation, reduction, or regulation of armaments between parties.
- 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.