Triple
T29304374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniProt REST API |
E743049
|
entity |
| Predicate | hasBaseUrl |
P83864
|
FINISHED |
| Object | https://rest.uniprot.org |
—
|
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: https://rest.uniprot.org | Statement: [UniProt REST API, hasBaseUrl, https://rest.uniprot.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseUrl Context triple: [UniProt REST API, hasBaseUrl, https://rest.uniprot.org]
-
A.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
B.
hasPrimaryURL
chosen
Indicates that an entity is associated with its main or canonical web address (URL).
-
C.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
D.
hasBaseOn
Indicates that one entity is supported by, rests upon, or is structurally or conceptually founded on another entity.
-
E.
hasBaseSpace
Indicates that one entity is defined or structured with respect to another entity that serves as its underlying base space.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 1:12 p.m.