Triple
T4784937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REGN-EB3 |
E106452
|
entity |
| Predicate | antibodyClass |
P24608
|
FINISHED |
| Object | IgG1 |
—
|
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: IgG1 | Statement: [REGN-EB3, antibodyClass, IgG1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antibodyClass Context triple: [REGN-EB3, antibodyClass, IgG1]
-
A.
antibodyType
chosen
Indicates the specific class or subtype of an antibody involved in the described relationship or context.
-
B.
antigen
Indicates that one entity functions as an antigen in relation to another, typically provoking or being recognized by an immune response.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
hasChemicalClass
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
-
E.
immuneResponseType
Indicates the specific kind or category of immune reaction that occurs in response to a particular stimulus or agent.
- 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_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. |
Created at: March 20, 2026, 1:22 p.m.