Triple
T27636776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Store (NgRx) |
E696491
|
entity |
| Predicate | updatesStateVia |
P114212
|
FINISHED |
| Object | reducers |
—
|
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: reducers | Statement: [Store (NgRx), updatesStateVia, reducers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesStateVia Context triple: [Store (NgRx), updatesStateVia, reducers]
-
A.
updatableVia
chosen
Indicates that one entity can be modified, refreshed, or brought up to date through the use, action, or mediation of another entity.
-
B.
updatesFrom
Indicates that one entity is revised, modified, or brought to a newer state based on information, changes, or content originating from another entity.
-
C.
cloneStateUpdated
Indicates that the state of a clone entity has been modified or refreshed from its previous condition.
-
D.
alsoFromState
Indicates that two entities originate from, are associated with, or come from the same state or region.
-
E.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:24 p.m.