Triple
T10521772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WritableStreamDefaultController |
E248190
|
entity |
| Predicate | constructorAccessible |
P93392
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [WritableStreamDefaultController, constructorAccessible, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorAccessible Context triple: [WritableStreamDefaultController, constructorAccessible, false]
-
A.
alsoAccessibleFrom
Indicates that a location, resource, or entity can be reached or obtained not only from one specified source or path but from an additional source or path as well.
-
B.
constructorAccepts
chosen
Indicates that a constructor takes a specified parameter or set of parameters as part of its definition.
-
C.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
D.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
E.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.