Triple
T23473113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioSample database |
E570179
|
entity |
| Predicate | usesAccessionPrefix |
P152410
|
FINISHED |
| Object | SAMN |
—
|
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: SAMN | Statement: [BioSample database, usesAccessionPrefix, SAMN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAccessionPrefix Context triple: [BioSample database, usesAccessionPrefix, SAMN]
-
A.
hasAccessionIdentifier
Indicates that an entity is associated with a specific accession identifier used for cataloging or reference purposes.
-
B.
requiresForAccession
Indicates that one entity must be obtained, completed, or satisfied before another entity can be accessed, entered, or formally joined.
-
C.
accessionType
Indicates the manner or category by which something is acquired, added, or admitted into a collection, system, or status.
-
D.
accessionMethod
Indicates the process or means by which something is acquired, obtained, or added to a collection or system.
-
E.
titleBeforeAccession
Indicates that the specified title was held by an entity prior to its accession to a higher rank, office, or status.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70244208190bbd8f58ac16d4399 |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:58 p.m.