Triple
T22692318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN1 |
E561082
|
entity |
| Predicate | cellularComponentOfProduct |
P68689
|
FINISHED |
| Object | cytoplasm |
—
|
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: cytoplasm | Statement: [SMN1, cellularComponentOfProduct, cytoplasm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellularComponentOfProduct Context triple: [SMN1, cellularComponentOfProduct, cytoplasm]
-
A.
cellularComponent
chosen
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
-
B.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
C.
hardwareComponent
Indicates that one entity is a physical hardware part or module that is contained in, attached to, or functionally part of another hardware system or device.
-
D.
catalogPartOf
Indicates that one catalog item is a component, section, or subset of a larger catalog or cataloged collection.
-
E.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789ba0148190891781d05ec64f3c |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.