Triple
T9477927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD4+ T cells |
E228561
|
entity |
| Predicate | areActivatedBy |
P6232
|
FINISHED |
| Object | antigen-presenting cells |
—
|
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: antigen-presenting cells | Statement: [CD4+ T cells, areActivatedBy, antigen-presenting cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areActivatedBy Context triple: [CD4+ T cells, areActivatedBy, antigen-presenting cells]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
C.
enabledBy
chosen
Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
-
D.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
E.
activationType
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd801386948190890133f622ff360b |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.