Triple
T27621569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldman–Hodgkin–Katz equation |
E700591
|
entity |
| Predicate | typicallyIncludesIon |
P47767
|
FINISHED |
| Object | potassium ion |
—
|
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: potassium ion | Statement: [Goldman–Hodgkin–Katz equation, typicallyIncludesIon, potassium ion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyIncludesIon Context triple: [Goldman–Hodgkin–Katz equation, typicallyIncludesIon, potassium ion]
-
A.
usesIonType
chosen
Indicates that one entity employs or operates using a specific type of ion in its function or process.
-
B.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
-
D.
sometimesIncluded
Indicates that one entity is occasionally, but not always, contained within, part of, or present in association with another entity.
-
E.
panelIncludes
Indicates that a panel or composite display element contains or incorporates a specified subcomponent or item as part of its structure or content.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: April 27, 2026, 2:14 p.m.