Triple
T10328491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStream |
E242819
|
entity |
| Predicate | chunkType |
P9638
|
FINISHED |
| Object | usually Uint8Array for byte streams |
—
|
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: usually Uint8Array for byte streams | Statement: [ReadableStream, chunkType, usually Uint8Array for byte streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chunkType Context triple: [ReadableStream, chunkType, usually Uint8Array for byte streams]
-
A.
blockType
Indicates that one entity is classified as a specific type or category of block in relation to another entity.
-
B.
typicalSegmentType
chosen
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
C.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
D.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
E.
spanType
Indicates the specific category or kind of span that characterizes the relationship or action between entities.
- 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_69d4d7cf21e08190bf605daeea0d9dcf |
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.