Triple
T10328628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStreamDefaultReader |
E242822
|
entity |
| Predicate | lockBehavior |
P93412
|
FINISHED |
| Object | locks the stream while reader is active |
—
|
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: locks the stream while reader is active | Statement: [ReadableStreamDefaultReader, lockBehavior, locks the stream while reader is active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockBehavior Context triple: [ReadableStreamDefaultReader, lockBehavior, locks the stream while reader is active]
-
A.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
B.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
C.
lockName
Indicates that an entity has or is associated with a specific lock identifier or name used to distinguish it from other locks.
-
D.
locks
Indicates that one entity secures, fastens, or restricts access to another entity, typically preventing its use or opening without proper authorization or a key.
-
E.
lockSystemSupplied
Indicates that a system-provided locking mechanism is used to control access or state, rather than a custom or user-defined lock.
- 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.