Triple
T10214658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixifi |
E242410
|
entity |
| Predicate | hasImmunoglobulinType |
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: [Ixifi, hasImmunoglobulinType, IgG1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmunoglobulinType Context triple: [Ixifi, hasImmunoglobulinType, IgG1]
-
A.
antibodyType
chosen
Indicates the specific class or subtype of an antibody involved in the described relationship or context.
-
B.
hasBloodTypeSystem
Indicates that an entity uses or is classified according to a particular blood type classification system (e.g., ABO, Rh).
-
C.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
-
D.
associatedWithAntibody
Indicates a relationship where something is linked or connected to a specific antibody, such as being produced by it, targeted by it, or otherwise functionally related to it.
-
E.
bloodType
Indicates that one entity has a specific blood group classification (such as A, B, AB, or O, with a positive or negative Rh factor).
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa273bdc8190bc4cf67a7923cebc |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:04 a.m.