Triple
T6004841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C9orf72 |
E133683
|
entity |
| Predicate | UniProtID |
P65649
|
FINISHED |
| Object | Q96LT7 |
—
|
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: Q96LT7 | Statement: [C9orf72, UniProtID, Q96LT7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UniProtID Context triple: [C9orf72, UniProtID, Q96LT7]
-
A.
EUAccession
Indicates that an entity becomes a member state of the European Union through the formal accession process.
-
B.
ontologyId
chosen
Indicates that there is an association between an entity and a specific ontology identifier that formally defines or classifies it within an ontology.
-
C.
typicalProtein
Indicates that one entity is a representative or characteristic example of a particular protein type or class.
-
D.
hasDrugBankID
Indicates that an entity is associated with a specific identifier from the DrugBank database.
-
E.
hasPubChemCID
Indicates that an entity (typically a chemical substance) is associated with a specific PubChem Compound Identifier (CID) in the PubChem database.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f10d18081908c351170b7f58d3d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.