Triple
T23466812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioProject database |
E569120
|
entity |
| Predicate | linksTogether |
P42454
|
FINISHED |
| Object | data from multiple NCBI databases |
—
|
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: data from multiple NCBI databases | Statement: [BioProject database, linksTogether, data from multiple NCBI databases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksTogether Context triple: [BioProject database, linksTogether, data from multiple NCBI databases]
-
A.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
-
B.
linkedPractice
Indicates that one practice is associated or connected to another practice in a meaningful or relevant way.
-
C.
linkedNetwork
chosen
Indicates that two entities are connected through a shared or associated network relationship.
-
D.
heldTogetherWith
Indicates that two or more entities are physically joined or kept in contact by some binding, fastening, or cohesive force.
-
E.
linkedToDate
Indicates that an entity is associated or connected to a specific date or point in time.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6fc35c48190a67614fb4170f15b |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.