Triple
T32378506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server-Sent Events |
E827349
|
entity |
| Predicate | clientEnvironment |
P9320
|
FINISHED |
| Object | web browsers |
—
|
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: web browsers | Statement: [Server-Sent Events, clientEnvironment, web browsers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientEnvironment Context triple: [Server-Sent Events, clientEnvironment, web browsers]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
hostedEnvironment
Indicates that one entity provides the runtime or operational environment in which another entity is deployed, executed, or made available.
-
C.
programEnvironment
Indicates the contextual setting, conditions, and resources within which a program operates or is executed.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
primaryOperatingEnvironment
chosen
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
- 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_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:51 a.m.