Triple
T29108203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pfam domain |
E736821
|
entity |
| Predicate | hasDatabaseAccessionPrefix |
P152410
|
FINISHED |
| Object | PF |
—
|
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: PF | Statement: [Pfam domain, hasDatabaseAccessionPrefix, PF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDatabaseAccessionPrefix Context triple: [Pfam domain, hasDatabaseAccessionPrefix, PF]
-
A.
usesAccessionPrefix
chosen
Indicates that one entity employs a specific accession prefix as part of its identifier or referencing scheme for another entity.
-
B.
hasAccessionIdentifier
Indicates that an entity is associated with a specific accession identifier used for cataloging or reference purposes.
-
C.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
D.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
E.
hasStationCodePrefix
Indicates that one entity’s station code begins with the prefix specified by the other entity.
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 11:16 a.m.