Triple
T22931924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniGene |
E569464
|
entity |
| Predicate | clusterCriterion |
P150299
|
FINISHED |
| Object | sequence similarity |
—
|
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: sequence similarity | Statement: [UniGene, clusterCriterion, sequence similarity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusterCriterion Context triple: [UniGene, clusterCriterion, sequence similarity]
-
A.
clusterConcentration
Indicates how densely the elements within a cluster are packed or distributed relative to one another.
-
B.
clusterStructure
Indicates that multiple entities are organized into a cluster, specifying how the elements are grouped and related within that clustered arrangement.
-
C.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
D.
clusterShape
Indicates the geometric form or configuration that a cluster of related items or points takes.
-
E.
CMeans
Indicates that one concept or entity conveys, expresses, or serves as the means by which another concept or entity is understood or represented.
- F. None of above. chosen
Provenance (4 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813260608190bb9e1ca704c7e12f |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:44 p.m.