Triple
T11074449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B lymphocytes |
E261828
|
entity |
| Predicate | developFrom |
P1245
|
FINISHED |
| Object | hematopoietic stem 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: hematopoietic stem cells | Statement: [B lymphocytes, developFrom, hematopoietic stem cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developFrom Context triple: [B lymphocytes, developFrom, hematopoietic stem cells]
-
A.
developmentFrom
Indicates that one entity arises, evolves, or is derived over time from another entity as a result of a developmental process.
-
B.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
C.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
D.
developsUntil
Indicates that a process, condition, or entity continues to develop or progress up to a specified point or limit in time or state.
-
E.
developmentFunction
Indicates a relationship where one entity serves as a function, role, or mechanism that drives, supports, or shapes the development or growth of 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994e32fc8190a6591d9e82b68f75 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.