Triple
T2373566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopfield network |
E46142
|
entity |
| Predicate | hasUpdateRule |
P7002
|
FINISHED |
| Object | asynchronous update |
—
|
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: asynchronous update | Statement: [Hopfield network, hasUpdateRule, asynchronous update]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpdateRule Context triple: [Hopfield network, hasUpdateRule, asynchronous update]
-
A.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
hasUpdatePolicy
chosen
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
-
C.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
D.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
-
E.
hasResultingChange
Indicates that one entity causes or leads to a specific change or transformation in another entity or state.
- 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.