Triple
T29108244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pfam domain |
E736821
|
entity |
| Predicate | hasPrimaryAccessURL |
P83864
|
FINISHED |
| Object | https://pfam.xfam.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://pfam.xfam.org | Statement: [Pfam domain, hasPrimaryAccessURL, https://pfam.xfam.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAccessURL Context triple: [Pfam domain, hasPrimaryAccessURL, https://pfam.xfam.org]
-
A.
hasPrimaryURL
chosen
Indicates that an entity is associated with its main or canonical web address (URL).
-
B.
hasPrimaryAccessFrom
Indicates that one entity serves as the main or preferred point of access or entry to another entity.
-
C.
hasPrimaryAccessType
Indicates that an entity is associated with its main or default mode or category of access.
-
D.
hasPrimaryAccessRole
Indicates that an entity is assigned the main or most authoritative access role governing its permissions or privileges.
-
E.
hasAccessURL
Indicates that an entity is associated with a specific URL through which it can be accessed or retrieved.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 28, 2026, 11:16 a.m.