Triple
T18531562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR-7 |
E452840
|
entity |
| Predicate | definesInterface |
P12981
|
FINISHED |
| Object | Psr\Http\Message\StreamInterface |
—
|
NE NERFINISHED |
How this triple was built (3 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: Psr\Http\Message\StreamInterface | Statement: [PSR-7, definesInterface, Psr\Http\Message\StreamInterface]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Psr\Http\Message\StreamInterface Context triple: [PSR-7, definesInterface, Psr\Http\Message\StreamInterface]
-
A.
PSR-7
PSR-7 is a PHP standard that defines common interfaces for HTTP messages, including requests and responses, to ensure interoperability between web frameworks and libraries.
-
B.
PSR-17
PSR-17 is a PHP standard that defines interfaces for HTTP message factories, enabling consistent creation of requests, responses, and related HTTP objects across frameworks and libraries.
-
C.
System.IO.Stream
System.IO.Stream is an abstract base class in .NET that represents a generic sequence of bytes and provides a common interface for reading from and writing to data sources such as files, memory, and network connections.
-
D.
ReadableStream
ReadableStream is a web platform interface representing a source of streaming data that can be read incrementally, commonly used for handling network responses and other asynchronous data flows in JavaScript.
-
E.
WHATWG Streams Standard
The WHATWG Streams Standard is a web platform specification that defines a unified, interoperable model and APIs for handling streaming data in web browsers and related environments.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Psr\Http\Message\StreamInterface Target entity description: Psr\Http\Message\StreamInterface is a PHP-FIG standard interface representing a stream of data used in HTTP messages, providing a consistent way to read from, write to, and manage message bodies in PSR-7–compliant applications.
-
A.
PSR-7
PSR-7 is a PHP standard that defines common interfaces for HTTP messages, including requests and responses, to ensure interoperability between web frameworks and libraries.
-
B.
PSR-17
PSR-17 is a PHP standard that defines interfaces for HTTP message factories, enabling consistent creation of requests, responses, and related HTTP objects across frameworks and libraries.
-
C.
System.IO.Stream
System.IO.Stream is an abstract base class in .NET that represents a generic sequence of bytes and provides a common interface for reading from and writing to data sources such as files, memory, and network connections.
-
D.
ReadableStream
ReadableStream is a web platform interface representing a source of streaming data that can be read incrementally, commonly used for handling network responses and other asynchronous data flows in JavaScript.
-
E.
WHATWG Streams Standard
The WHATWG Streams Standard is a web platform specification that defines a unified, interoperable model and APIs for handling streaming data in web browsers and related environments.
- F. None of above. chosen
Provenance (2 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fe35288190977c85ee0bb96264 |
completed | April 19, 2026, 7:58 p.m. |
Created at: April 10, 2026, 11:37 a.m.