Triple
T32378505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server-Sent Events |
E827349
|
entity |
| Predicate | clientAPI |
P8616
|
FINISHED |
| Object | EventSource interface |
—
|
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: EventSource interface | Statement: [Server-Sent Events, clientAPI, EventSource interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientAPI Context triple: [Server-Sent Events, clientAPI, EventSource interface]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
clientFor
chosen
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
C.
clientSDKPlatform
Indicates the software platform or environment on which a client-side SDK is designed to run or be used.
-
D.
clientServiceModel
Indicates a relationship where a particular service model is provided, managed, or applied for a given client.
-
E.
supportsAPIClientSDKs
Indicates that an entity provides or is compatible with software development kits (SDKs) intended for use by API clients.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c13307548190b3e209bff21ab524 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.