Triple
T22375229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket.IO |
E553135
|
entity |
| Predicate | clientRunsIn |
P11903
|
FINISHED |
| Object | web browser |
—
|
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 browser | Statement: [Socket.IO, clientRunsIn, web browser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientRunsIn Context triple: [Socket.IO, clientRunsIn, web browser]
-
A.
alsoRunsIn
Indicates that an entity (such as a program, process, or event) operates or occurs in an additional context, environment, or location beyond its primary one.
-
B.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
C.
canRunOn
chosen
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
D.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
E.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.