Triple
T2373597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopfield network |
E46142
|
entity |
| Predicate | hasActivationFunction |
P16017
|
FINISHED |
| Object | sign function |
—
|
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: sign function | Statement: [Hopfield network, hasActivationFunction, sign function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivationFunction Context triple: [Hopfield network, hasActivationFunction, sign function]
-
A.
activationFunction
chosen
Indicates the specific mathematical transformation applied to a neuron's input to produce its output in a computational or neural model.
-
B.
hasDistributionFunction
Indicates that an entity is associated with a specific distribution function that characterizes how its values or occurrences are probabilistically or statistically distributed.
-
C.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
D.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
E.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.