Triple
T2373571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopfield network |
E46142
|
entity |
| Predicate | stableStatesRepresent |
P11038
|
FINISHED |
| Object | stored patterns |
—
|
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: stored patterns | Statement: [Hopfield network, stableStatesRepresent, stored patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableStatesRepresent Context triple: [Hopfield network, stableStatesRepresent, stored patterns]
-
A.
stateRepresentation
chosen
Indicates that one entity serves as a depiction, model, or encoding of the condition, configuration, or status of another entity.
-
B.
stateRepresentationOfCandidate
Indicates that something serves as the official state-level representation or record associated with a particular candidate.
-
C.
supportsFormOfState
Indicates that one entity endorses, upholds, or favors a particular form or system of state governance associated with another entity.
-
D.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
-
E.
numberOfStatesRepresented
Indicates how many distinct states are represented or covered in a given context or 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.