Triple
T10328674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStreamBYOBReader |
E242823
|
entity |
| Predicate | promiseProperty |
P93419
|
FINISHED |
| Object | closed resolves when the stream closes |
—
|
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: closed resolves when the stream closes | Statement: [ReadableStreamBYOBReader, promiseProperty, closed resolves when the stream closes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promiseProperty Context triple: [ReadableStreamBYOBReader, promiseProperty, closed resolves when the stream closes]
-
A.
promiseScope
Indicates that one entity has made a commitment or assurance to another entity regarding a specific action, condition, or outcome within a defined scope or context.
-
B.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
C.
corePromise
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
-
D.
hasPromiseType
Indicates that an entity is associated with, or classified by, a specific type or category of promise.
-
E.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.