Triple
T4784956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REGN-EB3 |
E106452
|
entity |
| Predicate | combinationType |
P58402
|
FINISHED |
| Object | fixed-dose combination of three antibodies |
—
|
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: fixed-dose combination of three antibodies | Statement: [REGN-EB3, combinationType, fixed-dose combination of three antibodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinationType Context triple: [REGN-EB3, combinationType, fixed-dose combination of three antibodies]
-
A.
originalCombinationFor
Indicates that one entity is the initial or source combination from which another combined entity is derived or constructed.
-
B.
compositionForm
Indicates the structural or organizational form in which something is composed or arranged.
-
C.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
D.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
-
E.
hasComb
Indicates that an entity possesses or is equipped with a comb.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ae49ec81908f16248d22d1155f |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.