Triple
T10328478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStream |
E242819
|
entity |
| Predicate | supportsAsynchronousPull |
P93396
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ReadableStream, supportsAsynchronousPull, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAsynchronousPull Context triple: [ReadableStream, supportsAsynchronousPull, true]
-
A.
isAsynchronous
Indicates that the related process, operation, or interaction occurs without requiring simultaneous timing or immediate coordination between the involved entities.
-
B.
usesPushPullOperation
Indicates that one entity performs or relies on a push–pull mechanism or process in relation to another entity or system.
-
C.
isSynchronous
Indicates that two or more processes, events, or actions occur at the same time or in a coordinated, lockstep manner.
-
D.
supportsBatchProcessing
Indicates that the subject can handle multiple items or tasks in a single grouped operation rather than processing them individually.
-
E.
supportsSuspension
Indicates that one entity provides the necessary structure, strength, or mechanism to hold or keep another entity suspended.
- 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_69d4d7cf21e08190bf605daeea0d9dcf |
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.