Triple
T18531608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR-17 |
E452842
|
entity |
| Predicate | hasFullName |
P16
|
FINISHED |
| Object | PHP Standards Recommendation 17 |
—
|
NE NERFINISHED |
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: PHP Standards Recommendation 17 | Statement: [PSR-17, hasFullName, PHP Standards Recommendation 17]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PHP Standards Recommendation 17 Context triple: [PSR-17, hasFullName, PHP Standards Recommendation 17]
-
A.
PHP-FIG standards
PHP-FIG standards are a collection of community-driven PHP recommendations that define common interfaces and best practices to improve interoperability between PHP frameworks and libraries.
-
B.
PSR-16
PSR-16 is a PHP standard that defines a simple, interoperable caching interface for key-value storage.
-
C.
PSR-18
PSR-18 is a PHP-FIG standard that defines a common HTTP client interface for sending PSR-7 HTTP messages in PHP applications.
-
D.
PSR-15
PSR-15 is a PHP standard that defines interfaces for HTTP server request handlers and middleware to ensure interoperability between frameworks and libraries.
-
E.
PSR-17
chosen
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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.