Triple
T28938935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT |
E730391
|
entity |
| Predicate | hasReferenceProteinSequence |
P200662
|
FINISHED |
| Object | NP_002102 |
—
|
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: NP_002102 | Statement: [HTT, hasReferenceProteinSequence, NP_002102]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceProteinSequence Context triple: [HTT, hasReferenceProteinSequence, NP_002102]
-
A.
hasReferenceSequence
chosen
Indicates that an entity is associated with a specific canonical or reference sequence used as a standard for comparison or annotation.
-
B.
hasProteinFeature
Indicates that a protein possesses a specific structural or functional feature, such as a domain, motif, or modification site.
-
C.
hasProteinLength
Indicates the length or number of amino acids in a given protein.
-
D.
hasProtein
Indicates that one entity contains, includes, or is associated with a specific protein.
-
E.
hasProteinBinding
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: April 28, 2026, 8:34 a.m.