Triple
T28859097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monocercomonoides |
E728811
|
entity |
| Predicate | cellularCompartment |
P68689
|
FINISHED |
| Object | cytosol |
—
|
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: cytosol | Statement: [Monocercomonoides, cellularCompartment, cytosol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellularCompartment Context triple: [Monocercomonoides, cellularCompartment, cytosol]
-
A.
subcellularLocation
Indicates the specific location or compartment within a cell where an entity (such as a molecule or structure) is situated or functions.
-
B.
cellularComponent
chosen
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
-
C.
cellularOrganization
Indicates how the components within a biological cell are structured, arranged, and functionally organized in relation to one another.
-
D.
cellBiologyFeature
Indicates a relationship where a biological entity possesses or is characterized by a specific cellular-level property, structure, or function.
-
E.
cellStructure
Indicates the structural organization, components, and physical arrangement that make up a cell.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:46 a.m.