Triple
T9477922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD4+ T cells |
E228561
|
entity |
| Predicate | differentiateFrom |
P909
|
FINISHED |
| Object | common lymphoid progenitors |
—
|
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: common lymphoid progenitors | Statement: [CD4+ T cells, differentiateFrom, common lymphoid progenitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differentiateFrom Context triple: [CD4+ T cells, differentiateFrom, common lymphoid progenitors]
-
A.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
B.
differential
Indicates a relationship where one quantity or state is defined as the infinitesimal change or difference relative to another variable or function.
-
C.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
D.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
E.
differentiationProperty
Indicates a property or characteristic that serves to distinguish one entity from another within a given context.
- 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.