Triple
T10371862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadableStreamBYOBRequest |
E244401
|
entity |
| Predicate | webPlatformStatus |
P53877
|
FINISHED |
| Object | standardized |
—
|
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: standardized | Statement: [ReadableStreamBYOBRequest, webPlatformStatus, standardized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webPlatformStatus Context triple: [ReadableStreamBYOBRequest, webPlatformStatus, standardized]
-
A.
platformStatus
chosen
Indicates the current operational or availability state of a platform within a system or service context.
-
B.
websiteStatus
Indicates the current operational condition or availability state of a website.
-
C.
waterFrameworkStatus
Indicates the regulatory or ecological status of a water body as defined under a water framework or water management directive.
-
D.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
-
E.
serviceAvailability
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97ed09c8190a3627aa7b5eea62f |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.