Triple
T31440199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hematopoietic stem cells |
E802042
|
entity |
| Predicate | firstAppearIn |
P4114
|
FINISHED |
| Object | aorta-gonad-mesonephros region |
—
|
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: aorta-gonad-mesonephros region | Statement: [hematopoietic stem cells, firstAppearIn, aorta-gonad-mesonephros region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearIn Context triple: [hematopoietic stem cells, firstAppearIn, aorta-gonad-mesonephros region]
-
A.
firstAppearsAs
Indicates that an entity is introduced or shown in a particular form, role, or identity for the first time in a given context.
-
B.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
C.
firstAppearanceFor
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
-
D.
firstAppearanceAct
Indicates the act in which an entity makes its first appearance within a work or performance.
-
E.
firstNamedAppearance
Indicates the point or context in which an entity is first explicitly named or mentioned.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:05 p.m.