Triple
T10328639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStreamDefaultReader |
E242822
|
entity |
| Predicate | webIDLType |
P32473
|
FINISHED |
| Object | interface ReadableStreamDefaultReader |
—
|
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: interface ReadableStreamDefaultReader | Statement: [ReadableStreamDefaultReader, webIDLType, interface ReadableStreamDefaultReader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webIDLType Context triple: [ReadableStreamDefaultReader, webIDLType, interface ReadableStreamDefaultReader]
-
A.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
B.
definesElement
Indicates that one entity specifies or determines the nature, structure, or identity of another entity as its defining element.
-
C.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
D.
typeFamily
Indicates that one entity is classified as a family-related type or belongs to a family category in relation to another entity.
-
E.
baseType
chosen
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
- 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_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. |
Created at: April 6, 2026, 11:52 a.m.