Triple
T27636782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Store (NgRx) |
E696491
|
entity |
| Predicate | observableType |
P166654
|
FINISHED |
| Object | Observable |
—
|
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: Observable | Statement: [Store (NgRx), observableType, Observable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observableType Context triple: [Store (NgRx), observableType, Observable]
-
A.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
B.
observesType
Indicates that one entity observes, monitors, or takes note of another entity of a specified type.
-
C.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
D.
observerState
Indicates the condition, status, or configuration an observer is in at the time it perceives or monitors something.
-
E.
observableWith
Indicates that one entity can be detected, measured, or perceived through the use of another specified entity or method.
- F. None of above. chosen
Provenance (4 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_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 2:24 p.m.