Triple
T36600150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bursa of Fabricius |
E902893
|
entity |
| Predicate | roleInImmunity |
P95985
|
FINISHED |
| Object | humoral immunity |
—
|
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: humoral immunity | Statement: [bursa of Fabricius, roleInImmunity, humoral immunity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInImmunity Context triple: [bursa of Fabricius, roleInImmunity, humoral immunity]
-
A.
immunityType
Indicates the specific kind or category of immunity that applies in a given context (e.g., legal, diplomatic, medical).
-
B.
hasRoleInImmunity
chosen
Indicates that an entity functions in or contributes to an immune-related process or mechanism.
-
C.
immunity
Indicates that an entity is protected against or not affected by a particular agent, condition, or influence.
-
D.
roleInVaccineResponse
Indicates that one entity has a functional or regulatory involvement in the biological response to a vaccine associated with another entity.
-
E.
receivedImmunityFrom
Indicates that one entity has been granted protection or exemption (such as legal, medical, or other forms of immunity) by another entity.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01a48fbbd481908ccf75551dcf4647 |
completed | May 11, 2026, 9:42 a.m. |
| PD | Predicate disambiguation | batch_6a01a2d6db208190b11c1af601a544f5 |
completed | May 11, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:11 p.m.