Triple
T28740196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diplonemea |
E731214
|
entity |
| Predicate | molecularMarker |
P35223
|
FINISHED |
| Object | 18S rRNA gene |
—
|
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: 18S rRNA gene | Statement: [Diplonemea, molecularMarker, 18S rRNA gene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: molecularMarker Context triple: [Diplonemea, molecularMarker, 18S rRNA gene]
-
A.
phylogeneticMarker
chosen
Indicates that one entity serves as a genetic or molecular feature used to infer or represent the evolutionary relationships of another entity.
-
B.
molecularFunction
Indicates the specific biochemical activity or role that a molecule (typically a gene product or protein) performs at the molecular level.
-
C.
geneticElement
Indicates that one entity is a genetic element (such as a gene, sequence, or structural unit of genetic material) associated with or characterized by the other entity.
-
D.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
E.
morphologicalTraits
Indicates a relationship where specific physical form or structural characteristics are attributed to or associated with an 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b2b1808190a9f7c80eef2efa99 |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:02 a.m.