Triple
T10328575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransformStream |
E242821
|
entity |
| Predicate | defaultHighWaterMarkReadable |
P14460
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [TransformStream, defaultHighWaterMarkReadable, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultHighWaterMarkReadable Context triple: [TransformStream, defaultHighWaterMarkReadable, 1]
-
A.
highWaterMarkLocation
Indicates the specific place where the highest level reached by water is or was observed.
-
B.
maximumBodyLength
Indicates that there is an upper limit on the allowable length or size of a body (e.g., content, message, or object) in this relationship or action.
-
C.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
readsTo
Indicates that one entity reads or recites content aloud for the benefit of another entity.
-
E.
hasNotableReaderBase
Indicates that an entity is associated with a large, prominent, or otherwise noteworthy group of readers or audience.
- 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.