Triple
T34091345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nav1.1 sodium channel |
E874308
|
entity |
| Predicate | selectiveFor |
P66415
|
FINISHED |
| Object | Na+ ions |
—
|
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: Na+ ions | Statement: [Nav1.1 sodium channel, selectiveFor, Na+ ions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectiveFor Context triple: [Nav1.1 sodium channel, selectiveFor, Na+ ions]
-
A.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
B.
selectsFor
chosen
Indicates that one entity chooses or designates another entity as the preferred or targeted option from a set of possible candidates.
-
C.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
D.
alsoSelects
Indicates that an entity chooses or includes an additional option or item in conjunction with another already selected option or item.
-
E.
isSelectiveFire
Indicates that a firearm is capable of operating in multiple firing modes (such as semi-automatic and fully automatic) selectable by the user.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:52 a.m.